enterprise product integration

Enterprise Product IntegrationConfiguration and Troubleshooting Guide

Legal Information

Copyright NoticeCopyright © 2013 Flexera Software LLC. All Rights Reserved.

This product contains proprietary and confidential technology, information and creative works owned by Flexera Software LLC and its licensors, if any. Any use, copying, publication, distribution, display, modification, or transmission of such technology in whole or in part in any form or by any means without the prior express written permission of Flexera Software LLC is strictly prohibited. Except where expressly provided by Flexera Software LLC in writing, possession of this technology shall not be construed to confer any license or rights under any Flexera Software LLC intellectual property rights, whether by estoppel, implication, or otherwise.

All copies of the technology and related information, if allowed by Flexera Software LLC, must display this notice of copyright and ownership in full.

Intellectual PropertyFor a list of trademarks and patents that are owned by Flexera Software, see http://www.flexerasoftware.com/intellectual-property. All other brand and product names mentioned in Flexera Software products, product documentation, and marketing materials are the trademarks and registered trademarks of their respective owners.

Restricted Rights LegendThe Software is commercial computer software. If the user or licensee of the Software is an agency, department, or other entity of the United States Government, the use, duplication, reproduction, release, modification, disclosure, or transfer of the Software, or any related documentation of any kind, including technical data and manuals, is restricted by a license agreement or by the terms of this Agreement in accordance with Federal Acquisition Regulation 12.212 for civilian purposes and Defense Federal Acquisition Regulation Supplement 227.7202 for military purposes. The Software was developed fully at private expense. All other use is prohibited.

Book Name: Enterprise Product Integration Configuration and Troubleshooting Guide

Part Number: EPI-0200-IGCG

Product Release Date: August 29, 2013

http://www.flexerasoftware.com/intellectual-property

Contents

1 Enterprise Product Integration Configuration Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Contacting Us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2 Prerequisites for Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Install and Set Up Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Set Up Accounts and Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Establish Two-Way Trusts Between Multiple Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Configure Account Access Between Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

3 Installing and Configuring Flexera Service Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Flexera Service Gateway System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Installing the Flexera Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Frequently Asked Questions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

4 Configuring FlexNet Manager Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Testing FlexNet Manager Platform Server Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Connecting FlexNet Manager Platform to the Flexera Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Configuring FlexNet Manager Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Edit FlexNet Manager Platform Server Authentication Settings in IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Check That ManageSoftWebServiceAppPool Service is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Invoke GetTenants and GetFlexeraIDForApplication API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Import the Application Recognition Library (ARL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Resolving Active Directory “Double Hop” Issues Which Occur if FNMP and SQL Server are on Separate Computers .36

Viewing an Application’s Flexera ID in FlexNet Manager Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Enterprise Product Integration Configuration and Troubleshooting Guide / August 29, 2013 Edition EPI-0200-IGCG 3

Contents

5 Configuring App Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Testing App Portal Server Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Connecting App Portal to the Flexera Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Testing App Portal’s Connection to the Flexera Service Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Configuring App Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Edit App Portal Server Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Check the SelfService Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

Check the ESDService Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Test FlexNet Manager Platform Server Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

Invoke GetCategories API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Performing App Portal Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

HTTP 500.19 – Internal Server Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

If AdminStudio is Unable to Create a Catalog Item in App Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

6 Configuring AdminStudio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Connecting AdminStudio to the Flexera Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60

Testing AdminStudio’s Connection to the Flexera Service Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

View Flexera Identification Number in Application View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

View Flexera Service Gateway Messages During Import and Distribution to SCCM . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Configuring Authentication in Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

7 Configuring Workflow Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Connecting Workflow Manager to the Flexera Service Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Testing Workflow Manager’s Connection to the Flexera Service Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

4 EPI-0200-IGCG Enterprise Product Integration Configuration and Troubleshooting Guide / August 29, 2013 Edition

1
Enterprise Product Integration Configuration Guide
Flexera Software has developed a unified application usage management solution—comprised of FlexNet Manager Platform, AdminStudio, App Portal, and Workflow Manager—which gives you a consolidated and centralized approach to maximizing software value and optimizing usage across the application life cycle.

This guide explains how to configure and test this enterprise product integration solution.

Table 1-1 • Enterprise Product Integration Installation and Configuration

Section Description

Prerequisites for Integration Describes steps to take before implementing product integration.

Installing and Configuring Flexera Service Gateway

Explains how to install the Flexera Service Gateway.

Configuring FlexNet Manager Platform

Explains how to connect FlexNet Manager Platform to the Flexera Service Gateway, test the connection, and perform configuration steps.

Configuring App Portal Explains how to connect App Portal to the Flexera Service Gateway, test the connection, and perform configuration and troubleshooting.

Configuring AdminStudio Explains how to connect AdminStudio to the Flexera Service Gateway and to test the connection.

Configuring Workflow Manager Explains how to connect Workflow Manager to the Flexera Service Gateway and test the connection.


Chapter 1: Enterprise Product Integration Configuration GuideContacting Us

Contacting UsYou may contact us from anywhere in the world by visiting our website at:

http://www.flexerasoftware.com


http://www.flexerasoftware.com/company.htm

2
Prerequisites for Integration
The following tasks need to be performed prior to performing product integration:

• Install and Set Up Applications

• Set Up Accounts and Privileges

• Establish Two-Way Trusts Between Multiple Domains

• Configure Account Access Between Products

Install and Set Up ApplicationsIn order to implement the enterprise product integration solution, you need to first install and set up the following versions of these Flexera Software applications:

Table 2-1 • Installation Instructions for Flexera Software Applications

Application Version Installation and Setup Instructions

AdminStudio

Professional or Enterprise Edition

11.5 SP2 or later

To install and set up AdminStudio:

1. Install AdminStudio, as described in AdminStudio 2013 Installation Guide.

2. Open Application Manager and create an Application Catalog database on an SQL Server.

3. Import applications into the Application Catalog.


http://kb.flexerasoftware.com/doc/DocumentRepository/Installation/AdminStudio/AdminStudio%202013/01_Public/Product_Manual/AS2013InstallGuide.pdf

http://kb.flexerasoftware.com/doc/DocumentRepository/Installation/AdminStudio/AdminStudio%202013/01_Public/Product_Manual/AS2013InstallGuide.pdf

Chapter 2: Prerequisites for IntegrationInstall and Set Up Applications

App Portal 7.5.3 or later

To install and set up App Portal:

1. Install App Portal, as described in App Portal Installation Guide.

2. During installation, specify your SCCM database name, central site code, and global catalog server.

3. Create new software catalog items in App Portal.

FlexNet Manager Platform

9.2

To install and set up FlexNet Manager Platform:

1. Install FlexNet Manager Platform, as described in the FlexNet Manager Platform 9.2 Installation Guide, which is available from the Flexera Software Product and License Center.

2. Install the FlexNet Manager Platform and Flexera Inventory Manager Patch Q211574, which is available from the Flexera Software Product and License Center.

3. Import the FlexNet Manager Platform Application Recognition Library, as described in Import the Application Recognition Library (ARL).

Workflow Manager

6.5 or later

To install and set up Workflow Manager:

1. Install Workflow Manager, as described in the Workflow Manager 2013 Installation Guide.

2. Create companies and user accounts.

3. Create workflow templates and projects.

4. Submit workflow requests.

Note • In order for product integration to work, Workflow Manager cannot be installed on the same server as App Portal.

Table 2-1 • Installation Instructions for Flexera Software Applications

Application Version Installation and Setup Instructions


http://kb.flexerasoftware.com/doc/DocumentRepository/Installation/AdminStudio/Workflow%20Manager%202013/01_Public/Product%20Manual/WM2013InstallGuide.pdf

http://kb.flexerasoftware.com/doc/DocumentRepository/Installation/AdminStudio/Workflow%20Manager%202013/01_Public/Product%20Manual/WM2013InstallGuide.pdf

http://kb.flexerasoftware.com/doc/DocumentRepository/Installation/App%20Portal/App%20Portal%207.x/01_Public/Product_Manual/AppPortal752InstallGuide.pdf

Chapter 2: Prerequisites for IntegrationSet Up Accounts and Privileges

Set Up Accounts and PrivilegesThe Flexera Software Integrated Solution includes AdminStudio, App Portal, FlexNet Manager Platform, the Flexera Service Gateway, Workflow Manager, and Microsoft System Center Configuration Manager (SCCM). All of these products communicate over a company network to provide a complete packaging and deployment solution that tracks usage and reports licensing.

To enable the proper operation of each of these components, it is necessary to grant privileges to several accounts that run the software. The following table lists the accounts and the required privileges:

Table 2-2 • Accounts and Privileges in the Integrated Solution

Account Associated Product(s) Required Privileges

User account for packagers (AdminStudio users)

AdminStudio • Local workstation—Administrator privileges on the workstation where they are running AdminStudio

• SCCM—Application Administrator role

• FNMP—Read-Only User

• App Portal—Require administrator access so that they can create catalog items

• SQL Server—Database Owner (dbo) privileges on the AdminStudio database, if you will be using Windows Authentication on Workflow Manager. No privileges are required if you configure Workflow Manager with a SQL Server user account.

AMS_SYSTEM account

Workflow Manager • Must be a member of the local IIS_WPG group (or IIS_USRS) on the web server.

• Must have “modify” permissions on the Workflow Manager file share.

• Permission to send e-mail through the SMTP server.

• Permission to query Active Directory.

• If you will be calling any of the AdminStudio Platform APls in the iPlugin DLL, this account must be a member of the local Administrators group.

App Pool Identity Account

Workflow Manager • SQL Server—If you configure Workflow Manager to connect to SQL Server with Windows Authentication, the domain account that you specify for the App Pool needs Database Owner (dbo) privileges on the AdminStudio database.


Chapter 2: Prerequisites for IntegrationEstablish Two-Way Trusts Between Multiple Domains

Establish Two-Way Trusts Between Multiple Domains

Windows NT authentication is used to communicate across these integrated Flexera Software products. Therefore, if the customer’s environment contains multiple domains, and if your Flexera Software products are installed on different domains, it is recommended that all domains have two-way trusts between them.

App Pool Identity Account

App Portal • SCCM—Application Administrator

FNMP • FlexNet Manager Platform must be configured to work with Windows Authentication. If you install the database on a different server, then you need to enable the FlexNet Manager Platform server to be “Trusted for Delegation.”

• SCCM—This app pool account for FNMP needs to be trusted for delegation with the SQL Server computer. For instructions, see Resolving Active Directory “Double Hop” Issues Which Occur if FNMP and SQL Server are on Separate Computers

Flexera Service Gateway • Local user privileges on the server where it is installed.

• No additional permissions are required.

SCCM • Privileges to run SCCM, but no special privileges to any of the other products in the integrated solution.

AdminStudio users App Portal AdminStudio users need administrator access to App Portal so that they can create catalog items.

Table 2-2 • Accounts and Privileges in the Integrated Solution

Account Associated Product(s) Required Privileges


Chapter 2: Prerequisites for IntegrationConfigure Account Access Between Products

Configure Account Access Between ProductsWhen setting up these integrated Flexera Software products, you need to give certain accounts enhanced permissions to other products, as described in the following table:

Table 2-3 • Account Access Between Products

Account Needs ... Steps to Take

App Portal system account

Admin access to FlexNet Manager Platform

Give the App Portal system account administrative access to FlexNet Manager Platform.

Granting admin access to FlexNet Manager Platform means making the particular account (or operator) a member of the Compliance Admins role.

By default, a role named Compliance Admins is created when FlexNet Manager Platform is installed.

• In a single-tenant environment, the installing operator is assigned to the Compliance Admins role.

• In a multi-tenant environment, the first operator to start a console session for a newly-licensed tenant is assigned to the Compliance Admins role for that tenant.

However, any account can be made a member of the Compliance Admins role.

For instructions on how to add an account to a role, see Assigning an Operator to the Compliance Admins Role in FlexNet Manager Platform.

All the permissions required for FNMP are already set for the Compliance Admins role. No further configuration is required.



AdminStudio user accounts

Ability to authenticate against the FlexNet Manager Platform web service

AdminStudio does not run under a system account; only user accounts context as there are no access rights checks in the API code that is being called.

However, in order for the full integration with FlexNet Manager Platform, AdminStudio users do need access to FlexNet Manager Platform in order for the handshake to take place.

Specifically, AdminStudio users simply need to be able to authenticate against the FlexNet Manager Platform web service.

To enable authentication against the FlexNet Manager Platform web service:

1. Create a domain group.

2. Add all of the AdminStudio users who would be publishing within the catalog to that group.

3. If a read-only role does not exist in FlexNet Manager Platform, create one.

4. Because those users (or groups) need to have access to FlexNet Manager Platform, create them as Operators within FlexNet Manager Platform, and grant read-only access to the FlexNet Manager Platform system.

Administrator access to App Portal

AdminStudio users need administrator access to App Portal so that they can create catalog items.

FlexNet Manager System Account

Does not need access to AdminStudio or App Portal

The FlexNet Manager Platform system account does not need access to AdminStudio or App Portal because the communication is driven from the users of those products, not from FlexNet Manager Platform.

Table 2-3 • Account Access Between Products

Account Needs ... Steps to Take



Assigning an Operator to the Compliance Admins Role in FlexNet Manager Platform

To assign an operator to the Compliance Admins role, perform the following steps:

Task: To assign an operator the Compliance Admins role:

1. In the console tree, expand the Roles node to display a list of roles.

2. Click the name of any role to list operators assigned to that role, or click the Unassigned role to view operators that have not yet been assigned to roles. If the list of operators is long, you can filter it or sort it as required.

3. Select the operator (or operators) you will assign to a role.

4. Do one of the following:

• Click Add to role... if the operator is to remain in current roles in addition to the newly-assigned role.

• Click Move to role... if the newly-assigned role is to replace a current role.

The Add operators to a role dialog is displayed if you chose to add operators to a role. Otherwise the Assign members dialog is displayed.

Figure 2-1: Putting operators into a role, from which they take their access permissions

5. Select the Compliance Admins role.

6. Click OK.

The operator is assigned to the Compliance Admins role, and is immediately granted its access rights. If the operator has previously been assigned to another role, he or she will now have the combination of access rights granted by all assigned roles


3
Installing and Configuring Flexera Service Gateway
This chapter includes information on installing and using the Flexera Service Gateway, which is a component that enables AdminStudio, App Portal, Workflow Manager, and FlexNet Manager Platform to communicate.

• Flexera Service Gateway System Requirements

• Installing the Flexera Service Gateway

• Frequently Asked Questions


Chapter 3: Installing and Configuring Flexera Service GatewayFlexera Service Gateway System Requirements

Flexera Service Gateway System Requirements

The following table lists the recommended software and hardware configuration for a machine running the Flexera Service Gateway:

Table 3-1 • Flexera Service Gateway System Requirements

Requirement Description

Operating System Windows Server 2008 R2 or later

Processor 2 GHz Multicore processor

RAM 2 GB

Disk Space 250 MB

Java Java Runtime Environment 1.5 or above (included in the installation).

Ports to Open in Firewall

Clients access Flexera Service Gateway on ports 9443 and 8280 by default.


Chapter 3: Installing and Configuring Flexera Service GatewayInstalling the Flexera Service Gateway

Installing the Flexera Service GatewayTo install the Flexera Service Gateway, perform the following steps.

Note • It is recommended that you either install the Flexera Service Gateway on its own server or on the same

server as FlexNet Manager Platform. It is not recommended that it be installed on the same server as App Portal,

AdminStudio, or Workflow Manager.

Note • By default, the Flexera Service Gateway is installed on the C drive. To install it to an alternate drive, you need

to launch the installer using a command line, as described in Step 3 below.

Task: To install the Flexera Service Gateway:

1. Make sure that your server meets the requirements listed in Flexera Service Gateway System Requirements.

2. Download the Flexera Service Gateway installer from the Flexera Software Product & License Center.

3. Launch the installer in one of the following ways:

• To install Flexera Service Gateway to the default directory, which is your Program Files (x86) directory, double-click the FlexeraServiceGateway_v1.0.exe file.

• To install Flexera Service Gateway to an alternate directory or drive, use the following command line syntax to launch the installer:

FlexeraServiceGateway_v1.0.exe /V"INSTALLDIR=E:\MYDIRECTORY"

where E:\MYDIRECTORY is the desired installation location.



If the server does not already have Java Runtime Environment 1.5 or above installed, you will be prompted to install it.

If you are not prompted to install Java, skip to step 8.

4. Click Install. The Welcome panel of the Java SE Development Kit installer will open.



5. Click Next. The Custom Setup panel opens.

6. Accept the default selections and click Next. The Installing panel opens. You are then prompted to select a Destination Folder for the Java installation.

7. Accept the default location and click Next. Java is installed. When the installation is complete, a message stating that Java was successfully installed is displayed.



8. Click Finish. The Welcome panel of the Flexera Service Gateway installer opens.

Note • You may also be prompted to register your JDK.

9. Click Next. The License Agreement panel opens.



10. Accept the license agreement and click Next. The Ready to Install the Program panel opens.

11. Click Install. The Installing Flexera Service Gateway panel opens.



When installation is complete, the InstallShield Wizard Completed panel opens.

12. Click Finish.

13. Now, to check that Flexera Service Gateway is running, open the Services tab of Windows Task Manager.

14. Confirm that there is a service named WS02Carbon listed and that its status is Running.

15. Next, open each of the applications that you want to connect using the Flexera Service Gateway, and enter the name of the server where Flexera Service Gateway is installed.


Chapter 3: Installing and Configuring Flexera Service GatewayFrequently Asked Questions

Frequently Asked QuestionsThe following is a list of frequently asked questions regarding the Flexera Service Gateway.

What is Flexera Service Gateway?

Flexera Service Gateway is a fast, lightweight, open source Enterprise Service Bus implementation. It supports message routing, inter-mediation, transformation, logging, load balancing, fail over routing, task scheduling, eventing and much more.

What are the technologies used underneath Flexera Service Gateway?

Flexera Service Gateway is built on top of WSO2 Carbon, an OSGi based components framework for SOA. It uses Apache Synapse as the underlying mediation engine. Java is the primary programming language used to develop WSO2 ESB.

What is an Endpoint?

Endpoint is a target or collection of targets that a message can deliver.

Which Flexera Software products currently register endpoints with Flexera Service Gateway?

App Portal, AdminStudio, Workflow Manager, and FlexNet Manager Platform currently register endpoints with Flexera Service Gateway.

What is the database management system used in Flexera Service Gateway?

Flexera Service Gateway ships with an embedded H2 database.


Chapter 3: Installing and Configuring Flexera Service GatewayFrequently Asked Questions


4
Configuring FlexNet Manager Platform
When integrated with App Portal and AdminStudio, you can use FlexNet Manager Platform to automatically manage application licenses for App Portal catalog items. This section explains how to connect FlexNet Manager Platform to the Flexera Service Gateway so that it can communicate with App Portal and AdminStudio, and how to troubleshoot any issues that you might encounter.

• Testing FlexNet Manager Platform Server Authentication Settings

• Connecting FlexNet Manager Platform to the Flexera Service Gateway

• Configuring FlexNet Manager Platform

Important • To perform the steps in this chapter, you need to have already installed FlexNet Manager Platform 9.2

(including FlexNet Manager Platform and Flexera Inventory Manager Patch Q211574, which is available from the

Flexera Software Product and License Center).


Chapter 4: Configuring FlexNet Manager PlatformTesting FlexNet Manager Platform Server Authentication Settings

Testing FlexNet Manager Platform Server Authentication Settings

The first thing that you should do to prepare the FlexNet Manager Platform server for integration (even before connecting to the Flexera Service Gateway) is to attempt to browse to the FlexNet Manager Platform Compliance API Service documentation page to determine whether you are prompted to enter network credentials. This will test whether the server’s authentication settings are set properly.

Task: To test the FlexNet Manager Platform Server authentication settings:

1. On the FlexNet Manager Platform server machine, enter the following URL in a web browser:

http://<FNMPServer>/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx

such as:

http://win2008r2fnmp/ManageSoftServices/ComplianceAPIService/ComplianceAPIService.asmx

Tip • When identifying the FlexNet Manager Platform server in this URL, you can enter either the server name or

the server IP address.

The ComplianceAPIService page on the FlexNet Manager Platform server should open without prompting you to enter network credentials:


Chapter 4: Configuring FlexNet Manager PlatformTesting FlexNet Manager Platform Server Authentication Settings

If you are prompted to enter network credentials, then Windows Authentication is not set up correctly on the FlexNet Manager Platform server and you will need to modify its authentication settings. The problem could be an issue with the group policy settings for network authentication.

Note • If Windows Authentication is not enabled, App Portal and AdminStudio will be unable to communicate

with FlexNet Manager Platform.

2. To modify the authentication settings, see Edit FlexNet Manager Platform Server Authentication Settings in IIS. [add page number]


Chapter 4: Configuring FlexNet Manager PlatformConnecting FlexNet Manager Platform to the Flexera Service Gateway

Connecting FlexNet Manager Platform to the Flexera Service Gateway

FlexNet Manager Platform communicates with App Portal and AdminStudio via the Flexera Service Gateway component. To connect FlexNet Manager Platform to the Flexera Service Gateway, perform the following steps.

Task: To connect FlexNet Manager Platform to the Flexera Service Gateway:

1. In FlexNet Manager Platform, right-click the FlexNet Manager Platform node, and from the context menu select Properties. The FlexNet Manager Platform Properties dialog opens.

2. Select the Flexera Service Gateway tab.

3. Enter the host name of the computer running your implementation of Flexera Service Gateway.

• This should be in a form ready for insertion in a URL, such as an IP address, a machine name (provided that your DNS is fully configured), or a fully qualified domain name such as fsgserver.mycompany.com.

• If your implementations of Flexera Service Gateway and FlexNet Manager Platform are co-located on the same server, enter localhost.

• Do not provide the full URL, because this is created automatically.


Chapter 4: Configuring FlexNet Manager PlatformConfiguring FlexNet Manager Platform

Note • Instructions for installing the Flexera Service Gateway are found in Installing and Configuring Flexera

Service Gateway.

4. For Port, enter the port number for which Flexera Service Gateway has been configured. In a default implementation, this is port 9443.

5. In User name and Password, enter the credentials for the administrator account configured on Flexera Service Gateway.

Important • Unless your System Administrator has provided you with a specific user name and password to

use, enter the default User name value of admin and the default Password of admin.

Note • Keep a record of the password. All other details are stored in the registry for later recall, but for security

reasons, the password is not stored. You will only need the password again on rare occasions, such as on

rebuilding or relocating one of the servers, or after an upgrade to a later release of FlexNet Manager Platform

that enhances the API used by Flexera Service Gateway.

When all required information has been entered, the Register button is enabled.

6. Click Register. FlexNet Manager Platform contacts Flexera Service Gateway and registers its location and current API details.

• If the Flexera Service Gateway can be contacted, connection will be successful, and normal operations will continue in the background without further intervention.

• If the Flexera Service Gateway cannot be contacted, you will receive an error message.

Configuring FlexNet Manager PlatformIf other products connected to the Flexera Service Gateway are having trouble communicating with FlexNet Manager Platform, perform the following configuration tasks:

• Edit FlexNet Manager Platform Server Authentication Settings in IIS

• Check That ManageSoftWebServiceAppPool Service is Running

• Invoke GetTenants and GetFlexeraIDForApplication API

• Import the Application Recognition Library (ARL)

• Resolving Active Directory “Double Hop” Issues Which Occur if FNMP and SQL Server are on Separate Computers



Edit FlexNet Manager Platform Server Authentication Settings in IIS

To configure FlexNet Manager Platform authentication to avoid authentication issues, perform the following steps on the machine where FlexNet Manager Platform is installed.

Important • To address this issue, it is recommended that you consult with the network administrator at the

customer site.

Task: To configure FlexNet Manager Platform authentication in IIS:

1. Open Internet Information Services (IIS) 7.0 Manager.

2. Select ManageSoftServices in the tree. The Features view opens.



3. Double-click Authentication. The Authentication view opens.

4. Make sure that the following three options are set to Enabled:

• ASP.NET Impersonation

• Basic Authentication

• Windows Authentication

All other authentication methods should be set to Disabled.

Check That ManageSoftWebServiceAppPool Service is Running

To check that the ManageSoftWebServiceAppPool service is running, perform the following steps:

Task: To check the ManageSoftWebServiceAppPool service:


2. Select Application Pools in the tree. The Application Pools view opens.

3. In the Application Pools list, make sure that the ManageSoftWebServiceAppPool service is started and running under the NetworkService account.



Note • The NetworkService account has non-editable privileges configured by Microsoft that are sufficient for

FlexNet Manager Platform.

4. If the service is not started, start it by clicking Start in the Actions menu.

5. On the Actions menu, click Advanced Settings... to open the Advanced Settings dialog box for this service, and make sure that the Start Automatically property is set to True.

Invoke GetTenants and GetFlexeraIDForApplication API On the FlexNet Manager Platform server, once you are able to browse to the ComplianceAPIService without being prompted to log in (as described in Testing FlexNet Manager Platform Server Authentication Settings), try to invoke the GetTenants and GetFlexeraIDForApplication API. You should be able to invoke them without encountering any issues.

Task: To invoke GetTenants and GetFlexeraIDForApplication APIs:

1. On the FlexNet Manager Platform server machine, enter the following URL in a web browser:


such as:







2. Click on GetTenants in the list. If this API is working correctly, the following page should be displayed:



3. Return to the main ComplianceAPIService page and click on GetFlexeraIDForApplication in the list. If this API is working correctly, the following page should be displayed:

If an error message is displayed instead, FlexNet Manager Platform is not configured properly. One of the following could be causing this problem:

• Prevented by Active Directory policy—This type of error usually means that the System Administrator has changed the Active Directory policy so that it prevents the Flexera Software services from working.

• User does not have access to IIS—The user who is testing the connections may not have access to IIS if they are in the wrong security groups.



Import the Application Recognition Library (ARL)The FlexNet Manager Platform Import ManageSoft application recognition library scheduled task runs the application recognition and SKU library update tool. This tool downloads updates to FlexNet Manager Platform’s application recognition library (ARL), SKU library, and product use rights library (PURL) from the Flexera Software website.

You can use the Windows Task Scheduler system tool to modify the timing of the scheduled task or to modify the command line options used with the update tool (MgsImportRecognition.exe).

Task: To run the “Import ManageSoft application recognition library” scheduled task:

1. On the FlexNet Manager Platform server, launch the Task Scheduler.

2. Open the Import ManageSoft application recognition library task.

3. Modify the following settings to enable the Import ManageSoft application recognition library download task:

4. Run the task. It should complete within 30 minutes.

Setting Description

Default Schedule

This task is disabled by default, but it is set to run weekly at 1.00 a.m. each Sunday if enabled.

• If you want updates to occur weekly, enable this task.

• If you prefer to control when updates occur, leave it disabled and execute it manually at times convenient to you.

Default Command Line

"Prog-Drive:\Program Files\ManageSoft\Common\ndcrproc.exe"-e "Prog-Drive:\Program Files\ManageSoft\DotNet\bin\MgsImportRecognition.exe"-l "Prog-Drive:\Program Files\ManageSoft\DotNet\bin\MgsImportRecognition.exe" -oCREATE_NO_WINDOW=True



Resolving Active Directory “Double Hop” Issues Which Occur if FNMP and SQL Server are on Separate Computers

Important • You must perform this task if FlexNet Manager Platform and SQL Server are installed on separate

machines.

To enable Windows Authentication with FlexNet Manager Platform, the user’s credentials need to authenticate in two places:

• First “hop”—The user accesses IIS and authenticates into FlexNet Manager Platform.

• Second “hop”—FlexNet Manager Platform then uses that user’s credentials to connect to the FlexNet Manager Platform database on SQL Server.

For security reasons, IIS is not permitted to pass credentials to a secondary server. Therefore, if FlexNet Manager Platform and SQL Server are not installed on the same machine, IIS will be unable to perform the authentication, and an error will be generated.

If your enterprise’s security protocols require you install FlexNet Manager Platform and SQL Server on separate computers, you will need to enable a trusted delegation on the FlexNet Manager Platform computer to resolve this issue.

Note • For more information, see How to use the System.DirectoryServices namespace in ASP.NET on the Microsoft

Support site:

http://support.microsoft.com/default.aspx?scid=kb;en-us;329986

To enable a trusted delegation, perform the following steps on your FlexNet Manager Platform installation:

Task: To enable a trusted delegation:

1. Disable Anonymous Authentication for the following sites in IIS:

• ManageSoftServices

• ECMBusinessPortal

• ManageSoftECM

2. Ensure that only ASP.NET Impersonation and Windows Authentication are enabled for ManageSoftServices, ECMBusinessPortal and ManageSoftECM sites in IIS.





3. Clear the selection of the Enable Kernel mode authentication option for Windows Authentication on ManageSoftServices, ECMBusinessPortal and ManageSoftECM:

Note • You need to disable kernel-mode authentication because it only handles Kerberos authentication, but

does not allow delegation. You cannot have both Kernel-mode authentication enabled and also support

“double hop” authentication.

4. Create a new AD service account for handling delegation access for FlexNet Manager Platform.

5. In IIS, modify the ManageSoftWebServiceAppPool to use the newly created service account.



Note • You can choose to re-use the FNMP Service account instead of creating a new service account for the

purpose of delegation.

6. Remove all existing Service Principal Names (SPNs) on <FNMP Admin server> for IIS:

setspn -d http/<FNMP Admin Server> <FNMP Admin Server>setspn -d http/<FNMP Admin Server>:80 <FNMP Admin Server>setspn -d http/<FNMP Admin Server (Fully Qualified)> <FNMP Admin Server>setspn -d http/<FNMP Admin Server (Fully Qualified)>:80 <FNMP Admin Server>

7. Run setspn against the new service account user to create a Service Principal Name for the IIS process:

setspn -u -s http/<FNMP Admin Server> <FNMP service account user>setspn -u -s http/<FNMP Admin Server>:80 <FNMP service account user>setspn -u -s http/<FNMP Admin Server (Fully Qualified)> <FNMP service account user>setspn -u -s http/<FNMP Admin Server (Fully Qualified)>:80 <FNMP service account user>

Note • This will allow the FNMP service account user to authenticate users accessing IIS.

8. Ensure that the SQL Server service account has the necessary SPN created so it can authenticate users accessing the SQL server:

setspn -l <SQL Server user service account>

It should list the following:

….MSSQLSvc/<SQL Server Machine Name (Fully Qualified)>:1433 MSSQLSvc/<SQL Server Machine Name (Fully Qualified)>….

9. Create an SPN for the flat name as well in case SQL Server has issues discovering the short hand name of the server:

setspn -u -s MSSQLSvc/<SQL Server Machine Name>:1433 <SQL Server service user account>setspn -u -s MSSQLSvc/<SQL Server Machine Name> <SQL Server service user account>

10. Ensure that the SQL Server Reporting Services service account has the necessary SPN created so it can authenticate users accessing reports in the FNMP web portals:

setspn -u -a http/<SQL Server Machine Name> <SQL Server service user>setspn -u -s http/<SQL Server Machine Name>:80 <SQL Server service user>setspn -u -s http/<SQL Server Machine Name (Fully Qualified)> <SQL Server service user>setspn -u -s http/<SQL Server Machine Name (Fully Qualified)>:80 <SQL Server service user>

11. Enable Kerberos authentication on the SQL Server Reporting Services reports. (By default, it is disabled.)

12. On the SQL Server machine, edit:

<SQL Server Install Dir>\MSRS10_50.MSSLSERVER\Reporting Services\ReportServer\

rsreportserver.config

By default, it is installed at:

C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer



13. Add the RSWindowsNegotiate authentication type. For example, the <Authentication> subsection in the file should look something like this:

<Authentication><AuthenticationTypes>

<RSWindowsNegotiate/><RSWindowsNTLM/>

</AuthenticationTypes><RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel><RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario><EnableAuthPersistence>true</EnableAuthPersistence>

</Authentication>

14. Allow delegation for the <FNMP service account user> so it can delegate the user authentication token from FNMP to SQL Server and FNMP to SQL Server Reporting Services.

a. First, add the FNMP SQL Server service to give delegation access to the <FNMP service account user>.

b. Then, add the SQL Server Reporting Services service to give delegation access to the <FNMP service account user>.

The end result should look something similar to the following:

Figure 4-1: User Properties Dialog Box from Active Directory


Chapter 4: Configuring FlexNet Manager PlatformViewing an Application’s Flexera ID in FlexNet Manager Platform

Viewing an Application’s Flexera ID in FlexNet Manager Platform

The only place in the FlexNet Manager Platform user interface that you can view Flexera IDs for applications is in the Custom Views. To view the Flexera IDs, you need to create a new custom view.

Task: To create a new custom view for Flexera IDs:

1. In FlexNet Manager Platform, locate and expand the Custom Views node.

2. Select a folder, such as My Private Views, and select Add View from the context menu. The Custom View Properties dialog box opens.

3. On the General tab in the Name field, enter a name for the new custom view, such as Application with Flexera ID.



4. Open the Search Details tab, which displays a lists of objects that you can include in your view.

5. Add the Application object to the view. The appearance of the tab then switches to allow you to build the view further.

6. In the Properties column, select the Flexera ID and Name columns. (The Name column is selected by default.)

7. Click OK to save the view.

8. Navigate to the node for the new view.



9. Click Refresh. A view similar to the following opens:

Figure 4-2: FlexNet Manager Platform / Custom View - Application with Flexera ID


5
Configuring App Portal
When App Portal is integrated with FlexNet Manager Platform and AdminStudio licenses for App Portal catalog items can be managed automatically. This section explains how to connect App Portal to the Flexera Service Gateway so that it can communicate with FlexNet Manager Platform and AdminStudio, and how to troubleshoot any issues that you might encounter.

• Testing App Portal Server Authentication Settings

• Connecting App Portal to the Flexera Service Gateway

• Testing App Portal’s Connection to the Flexera Service Gateway

• Configuring App Portal

• Performing App Portal Troubleshooting


Chapter 5: Configuring App PortalTesting App Portal Server Authentication Settings

Testing App Portal Server Authentication Settings

The first thing that you should do to prepare the App Portal server for integration (even before connecting to the Flexera Service Gateway) is to attempt to browse to the App Portal Integration API Service documentation page to determine whether you are prompted to enter network credentials. This will test whether authentication settings of the App Portal server are set properly.

Task: To test the App Portal server authentication settings:

1. On the App Portal server machine, enter the following URL in a web browser:

http://<AppPortalServer>/ESD/WS/Integration.asmx

such as:

http://Win2008R2AppPortal/ESD/WS/Integration.asmx

Tip • When identifying the App Portal server in this URL, you can enter either the server name or the server IP

address.

The Integration documentation page on the App Portal server should open without prompting you to enter network credentials:

If you are prompted to enter network credentials, then Windows Authentication is not set up correctly on the App Portal server and you will need to modify its authentication settings. The problem could be an issue with the group policy settings for network authentication.


Chapter 5: Configuring App PortalConnecting App Portal to the Flexera Service Gateway

Note • If Windows Authentication is not enabled, FlexNet Manager Platform and AdminStudio will be unable to

communicate with App Portal.

2. To modify the authentication settings, see Edit App Portal Server Authentication Settings.

Connecting App Portal to the Flexera Service Gateway

App Portal communicates with FlexNet Manager Platform via the Flexera Service Gateway component. To connect App Portal to the Flexera Service Gateway, perform the following steps.

Task: To connect to the Flexera Service Gateway:

1. In App Portal, open the Admin tab.

2. Select Site Management > Settings. The General tab of the Settings view opens.

3. Open the Integration tab.

4. In the Flexera Service Gateway Server Name field, enter the name of your Flexera Service Gateway server.

5. Click Save.


Chapter 5: Configuring App PortalTesting App Portal’s Connection to the Flexera Service Gateway

Testing App Portal’s Connection to the Flexera Service Gateway

After you have performed the steps in Connecting App Portal to the Flexera Service Gateway, if FlexNet Manager Platform is also connected to the Flexera Service Gateway, you should be able to user App Portal to perform the following steps.

Task: To test App Portal’s connection to the Flexera Service Gateway:

1. Open App Portal.

2. Under Site Management on the Admin tab, select Catalog Management.

3. Under Current Catalog Items, select View All Items. Existing catalog items are listed.

4. Double-click on an existing catalog item. The Catalog Item Properties dialog box for that application opens.

5. Open the FlexNet Manager Platform tab.

6. Enter application information in the Product Name, Version, Edition, and Publisher fields, and then click Search.


Chapter 5: Configuring App PortalTesting App Portal’s Connection to the Flexera Service Gateway

7. From the list of search results, select the appropriate entry. The selected item will be highlighted.

8. Click Save. The catalog item is now mapped to a software entry in FlexNet Manager Platform, and the product information is now listed at the top of the dialog box.


Chapter 5: Configuring App PortalConfiguring App Portal

If the application is successfully mapped, it indicates that App Portal’s connection to FlexNet Manager Platform via the Flexera Service Gateway is configured properly.

9. If the application is not successfully mapped, see Configuring App Portal.

Configuring App PortalIf you are having trouble integrating App Portal, you should perform the following configuration tasks:

• Edit App Portal Server Authentication Settings

• Check the SelfService Service

• Check the ESDService Service

• Test FlexNet Manager Platform Server Authentication Settings

• Invoke GetCategories API



Edit App Portal Server Authentication SettingsTo edit the App Portal server authentication settings, perform the following steps.

Task: To edit App Portal server authentication settings:


2. Select ESD in the tree. The Features view opens.

3. Double-click Authentication. The Authentication view opens.



4. Make sure that Windows Authentication is set to Enabled, and that all other authentication methods are set to Disabled.

5. If you want to grant access to this site based on an IP address or domain name, go back to the IIS 7 Features view and double-click on IP Address and Domain Restrictions. The IP Address and Domain Restrictions view opens.

6. Click Add Allow Entry. The Add Allow Restriction Rule dialog box opens.

7. Enter the IP addresses that you want to be able to access the App Portal Site.

8. Click OK.



Check the SelfService ServiceTo check that the SelfService application pool service is running, perform the following steps:

Task: To check the SelfService application pool service:


2. Select Application Pools in the tree. The Application Pools view opens.

3. In the Application Pools list, make sure that the SelfService service is started and running under the domain account that was specified during the App Portal installation.





Check the ESDService ServiceTo check that App Portal’s ESDService service is running, perform the following steps:

Task: To check the ESDService service:

1. On the App Portal server machine, open the Microsoft Management Console Services dialog box.

2. Locate ESDService in the list and make sure that the Status is set to Started and that the Log On As column is set to the domain account that was specified during the App Portal installation.





Test FlexNet Manager Platform Server Authentication Settings

To test the FlexNet Manager Platform server authentication settings, you need to browse to the FlexNet Manager Platform Compliance API Service documentation page to determine whether you are prompted to enter network credentials. This will test whether the authentication settings of the FlexNet Manager Platform server are set properly.

Task: To test the FlexNet Manager Platform server authentication settings:



such as:





If you are prompted to enter network credentials, then Windows Authentication is not set up correctly on the FlexNet Manager Platform server and you will need to modify its authentication settings.



Note • If Windows Authentication is not enabled on the FlexNet Manager Platform server, App Portal will be

unable to communicate with FlexNet Manager Platform.

2. To modify the FlexNet Manager Platform server authentication settings, see Edit FlexNet Manager Platform Server Authentication Settings in IIS.

Invoke GetCategories API On the App Portal server, once you are able to browse to the Compliance API Service without being prompted to log in (as described in Testing App Portal Server Authentication Settings), try to invoke the GetCategories API. You should be able to invoke it without encountering any issues.

Task: To invoke GetCategories API:


http://<AppPortalServer>/ESD/WS/Integration.asmx

such as:

http://Win2008R2AppPortal/ESD/WS/Integration.asmx

Tip • When identifying the App Portal server in this URL, you can enter either the server name or the server IP

address.



The Integration documentation page on the App Portal server should open without prompting you to enter network credentials:

2. Click on GetCategories in the list. If this API is working correctly, the following page should be displayed:


Chapter 5: Configuring App PortalPerforming App Portal Troubleshooting

If an error message is displayed instead, App Portal is not configured properly. One of the following could be causing this problem:

• Prevented by Active Directory policy—This type of error usually means that the System Administrator has changed the Active Directory policy so that it prevents the Flexera Software services from working.

• User does not have access to IIS—The user who is testing the connection may not have access to IIS if they are in the wrong security groups.

Performing App Portal TroubleshootingDuring the integration of App Portal, the following issues have been reported:

• HTTP 500.19 – Internal Server Error

HTTP 500.19 – Internal Server Error

Problem

When you attempt to launch App Portal in a browser, you receive the following error:

HTTP 500.19 – Internal Server Error: The requested page cannot be accessed because the related configuration data for the page is invalid

Resolution

To resolve this error, run the following command:

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

Note • You are only required to run this command one time, not each time App Portal is launched.

Note • The resolution to this error is documented in the following KB article:

Q207028: ERRDOC: WSUS and X64 - HTTP Error 500.19 - Internal Server Error


http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q207028&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=145121017&stateId=0%200%20145115596


If AdminStudio is Unable to Create a Catalog Item in App Portal

If both AdminStudio and App Portal are connected via the Flexera Service Gateway, when you publish an application from AdminStudio to System Center 2012 Configuration Manager, a catalog item for that application should automatically be created in App Portal (in the default catalog category). Both the App Portal catalog item and the AdminStudio application will be identified by the same Flexera ID.

If a catalog item fails to be created, it may be because App Portal no longer has a Default Category specified. This can occur if the existing default category is deleted in App Portal. If the existing default category is deleted, the Default Category field on the Settings > Web Site > General tab is set to -Select-:

Figure 5-1: Default Category Field on Web Site > General Tab

In order for AdminStudio to automatically create an App Portal catalog item during publication, App Portal’s default category must be set to a valid category. To attempt to resolve this issue, select an existing category from the Default Category list.


6
Configuring AdminStudio
AdminStudio 11.5 SP2 or later can be integrated with App Portal and FlexNet Manager Platform via the Flexera Service Gateway. When AdminStudio is integrated, the following occurs:

• AdminStudio obtains the Flexera ID from FlexNet Manager Platform—When an application is imported into the Application Catalog, AdminStudio will automatically query the FlexNet Manager Platform ARL and obtain the application’s Flexera ID.

• AdminStudio creates catalog item in App Portal—When an application is published from AdminStudio to System Center 2012 Configuration Manager, a catalog item for that application will automatically be created in App Portal.

The following sections explain how to configure AdminStudio:

• Connecting AdminStudio to the Flexera Service Gateway

• Testing AdminStudio’s Connection to the Flexera Service Gateway

• Configuring Authentication in Internet Explorer


Chapter 6: Configuring AdminStudioConnecting AdminStudio to the Flexera Service Gateway

Connecting AdminStudio to the Flexera Service Gateway

To enable AdminStudio to communicate with App Portal and FlexNet Manager Platform via the Flexera Service Gateway, perform the following steps:

Task: To enter Flexera Service Gateway connection settings:

1. Open Application Manager.

2. On the Application Manager tab menu, select Options. The Options dialog box opens.

3. Under Servers Options, select Flexera Service Gateway. The Flexera Service Gateway tab opens.

4. Enter the following information:

• Flexera Service URL—Enter the name or URL of your Flexera Service Gateway server. If your System Administrator has installed Flexera Service Gateway using a different port than the default port, enter the appropriate port number at the end of the URL, preceded by a colon, such as: 172.300.40.501:8484

• User Name—Unless your System Administrator has provided you with a specific User Name to use, enter the default value of admin.

• Password—Unless your System Administrator has provided you with a specific Password to use, enter the default value of admin.

5. Click Test to validate the Flexera Service Gateway connection information.


Chapter 6: Configuring AdminStudioConnecting AdminStudio to the Flexera Service Gateway

6. Under Synchronize Flexera Products, click the FlexNet Manager Platform button to search the FlexNet Manager Platform Application Recognition Library (ARL) to locate and obtain the Flexera Identification Number for the Application Catalog’s existing applications.

Note • After valid Flexera Service Gateway connection information is entered, each time you import an

application into the Application Catalog, the Flexera Identification Number for that application will be

automatically obtained from FlexNet Manager Platform.

7. Click the App Portal button to create a catalog item in App Portal for all of the applications in the Application Catalog that were published to System Center Configuration Manager before the Flexera Service Gateway connection information was entered.

Note • After valid Flexera Service Gateway connection information is entered, each time you publish an

application to System Center 2012 Configuration Manager, a catalog item for that application will automatically

be created in App Portal.

8. Click OK.


Chapter 6: Configuring AdminStudioTesting AdminStudio’s Connection to the Flexera Service Gateway

Testing AdminStudio’s Connection to the Flexera Service Gateway

If AdminStudio is successfully connected to the Flexera Service Gateway (as described in Connecting AdminStudio to the Flexera Service Gateway), and if FlexNet Manager Platform is also connected, a Flexera Identification Number will be displayed on the General Information tab of an application's Application View. Also, messages related to the Flexera Identification Number will be displayed during application import and publication to System Center 2012 Configuration Manager.

• View Flexera Identification Number in Application View

• View Flexera Service Gateway Messages During Import and Distribution to SCCM

View Flexera Identification Number in Application ViewIf AdminStudio is successfully connected to the Flexera Service Gateway (as described in Connecting AdminStudio to the Flexera Service Gateway), and if FlexNet Manager Platform is also connected, a Flexera Identification Number will be displayed on the General Information tab of an application's Application View.

Task: To view an application’s Flexera Identification Number:

1. Open Application Manager.

2. On the Catalog tab, select an application in the tree. The Application View opens.

3. Note that an ID number is displayed in the Flexera Identification Number field, such as:

arl://MGS-APP-00000125196


Chapter 6: Configuring AdminStudioTesting AdminStudio’s Connection to the Flexera Service Gateway

View Flexera Service Gateway Messages During Import and Distribution to SCCM

When AdminStudio is connected to the Flexera Service Gateway, additional output messages appear each time you import an application into the Application Catalog or publish an application to System Center 2012 Configuration Manager. To view these messages, perform the following steps:

Task: To view Flexera Service Gateway messages during import and distribution to SCCM:

1. Using Application Manager, import an application into the Application Catalog. The following messages will be listed on the Import tab of the Output Window:

Extracting Flexera Identification Number from FlexNet Manager Platform...Done with extracting Flexera Identification Number from FlexNet Manager Platform

2. Using Distribution Wizard, publish an application to System Center 2012 Configuration Manager. The following messages will be listed on the Distribution Output panel of the Distribution Wizard:

Sending publish notification to Flexera Gateway Service.Publish notification result from Flexera Gateway Service: Success.


Chapter 6: Configuring AdminStudioConfiguring Authentication in Internet Explorer

Configuring Authentication in Internet Explorer

To configure authentication in Internet Explorer so that you can access FlexNet Manager Platform from AdminStudio, perform the following steps:

Task: To configure authentication in Internet Explorer:

1. On the AdminStudio machine, enter the following URL in the Internet Explorer web browser:


such as:




You will then be prompted to login to this server.

2. Enter the login credentials for this server and click OK.The ComplianceAPIService page on the FlexNet Manager Platform server opens:

3. Select Tools > Internet Options. The Internet Options dialog box opens.

4. Open the Security tab.



5. Select the Local intranet zone.

6. Click Sites. The Local intranet dialog box opens, with the current site (http://win2008r2fnmp) listed in the Add this website to the zone field.

7. Click Add. The site name is now listed in the Websites list.

8. Click Close to close the Local intranet dialog box and click OK to close the Intranet Options dialog box.


7
Configuring Workflow Manager
When Workflow Manager is connected to the Flexera Service Gateway, you can connect an App Portal catalog item to a Workflow Manager workflow request.

• Connecting Workflow Manager to the Flexera Service Gateway

• Testing Workflow Manager’s Connection to the Flexera Service Gateway


Chapter 7: Configuring Workflow ManagerConnecting Workflow Manager to the Flexera Service Gateway

Connecting Workflow Manager to the Flexera Service Gateway

To connect Workflow Manager to the Flexera Service Gateway, perform the following steps:

Task: To connect to the Flexera Service Gateway:

1. In Workflow Manager, open the System Settings subtab of the Administration tab.

2. Under Register With Flexera Service Gateway, enter the following information:

• Workflow Manager Portal Server—Enter the name of your Workflow Manager portal server.

• Flexera Service Gateway Server—Enter the name of your Flexera Service Gateway Server.

3. Click Update.


Chapter 7: Configuring Workflow ManagerTesting Workflow Manager’s Connection to the Flexera Service Gateway

Testing Workflow Manager’s Connection to the Flexera Service Gateway

To test Workflow Manager’s connection to the Flexera Service Gateway, perform the following steps:

Task: To test Workflow Manager’s connection to the Flexera Service Gateway:

1. In App Portal, open the Actions tab of a catalog item’s Catalog Item Properties dialog box.

2. Under Current Events and Actions, select an event that you want to trigger a Workflow Manager workflow (such as On Submit Approval).

3. Under Add an action, select Workflow Manager Action from the first list and Submit Workflow from the second list.

4. Under Select Workflow Manager Project, select a project from the list.

5. Click Add.

6. On the Browse Catalog tab, submit a workflow request for this catalog item.

7. Open Workflow Manager to see if a workflow request was automatically created for this catalog item.

8. In Workflow Manager, complete the workflow request.

9. Open App Portal and confirm that the status of the catalog item request has changed to Complete.


Chapter 7: Configuring Workflow ManagerTesting Workflow Manager’s Connection to the Flexera Service Gateway


enterprise product integration

Documents