IBM Control Desk 7.5.3

Transcription

1 IBM IBM Control Desk Integrating with IBM Endpoint Manager for Software Deployment Version 1.0 1

2 Copyright International Business Machines Corporation US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 2

3 CONTENTS Table of Contents Contents Introduction Prerequisites Downloading and installing the package Importing data from Endpoint Manager into Control Desk Importing data from Software Knowledge Base Toolkit into Control Desk (optional) Setting up the Jython library Promoting deployed asset data to authorized assets Integrating Control Desk with IBM Endpoint Manager Creating Software Offerings for your Enterprise App Store...18 Verifying the integration Deploying licensed software to assets Prerequisite Deploy Licensed Software to Multiple Assets Deploy Multiple Licensed Software to a Single Asset Re-image an Asset De-allocate Licenses when Asset is Decommissioned Troubleshooting...33 Appendix 1: Manual steps to integrate Control Desk with Endpoint Manager...34 Step 1: Specify an end point for connecting to the IEM server...34 Step 2: Create a software record in the Software Catalog...35 Step 3: Import the Endpoint Manager server certificate into WebSphere Application Server...36 Step 4: Create a license for the software...37 Step 5: Activate the escalation...38 Step 6: Verify the integration

4 1. Introduction This document describes a content package that you can use to integrate IBM Endpoint Manager with IBM Control Desk. The package is available in the ISM Content Library. With this package, you can deploy licensed software to assets automatically using Endpoint Manager and manage software license allocation using offerings that are included in the package. The following three packages are provided in the content package: 1. Content Installer package containing offerings and catalog (IBM_Endpoint_Manager_Software_Distribution.zip). This package contains a set of offerings that you can use to distribute software to multiple assets, distribute multiple software packages to a single asset, and re-image an asset. This is installable through the ISM Content Installer application. 2. Endpoint Manager Integration Enablement PMP package (iem_swd_base.zip). This package contains artefacts that are required for the integration, including classifications, job plans, automation scripts, workflows, actions, escalations, endpoints, signature options. This PMP package is installable through the Process Solution Installer command. 3. Endpoint Manager Integration Configuration PMP package (iemcfg_pmp.zip). This package helps simplify the setup of the integration with IEM and facilitates software deployment in an enterprise app store. This PMP package is installable through the Process Solution Installer command. The first two packages when installed together provide the ability to integrate Control Desk and Endpoint Manager, in addition to providing several options for deploying licensed software to assets. The third package Endpoint Manager Integration Configuration package contains a configuration tool that facilitates configuration of the integration with Endpoint Manager. It also enables you to build an IBM Control Desk Service Catalog offering to distribute a specified software product in the IBM Control Desk Self Service Center, your enterprise app store. Overview of automated software deployments Automated software provisioning is based on the integration of IBM Control Desk with IBM Endpoint Manager (IEM). This guide describes how to integrate the two products when you have them installed in your local environment. A first step is to decide which software applications to offer to users for automatic deployment. In IBM Endpoint Manager you define the deployable software distribution packages and the tasks that are associated with deploying the packages. Using Integration Composer with IBM Endpoint Manager, you can import discovered data about software into Control Desk. You typically populate the Software Catalog application in Control Desk by importing the software catalog data that is provided by the Software Knowledge Base Toolkit. When this integration is complete, Control Desk users can request a software product in the Self Service Center, and the requested software is automatically deployed to their computer by Endpoint Manager. 4

5 The following image illustrates the workflow for this integration. 1. Software packages are published in the Control Desk Self-Service Center catalog. 2. User requests software. 3. Workflow is initiated. 4. Optional: Automatic or manual approvals occur based on corporate policy. (The default is automatic.) 5. Workflow calls Endpoint Manager to deploy the software if there are enough licenses available. If not, a task is created for the license administrator to procure more licenses. 6. Endpoint Manager deploys software to the target. 7. Status of the IEM action is checked periodically. 8. If the deployment is successful, the license is allocated to the asset; otherwise, a task is created for the task administrator to investigate. The following sections of this document describe the tasks you need to perform to use this content package: install the packages and configure the integration between Control Desk and Endpoint Manager create deployable software offerings and publish in the Self Service application, your enterprise app store deploy licensed software to assets 5

6 2. Prerequisites Before you begin the integration process, you must install and configure the following products: IBM Control Desk Version For installation instructions, see Installing Control Desk. IBM Integration Composer Version You can install Integration Composer as part of the Control Desk installation. Note that Java 6 is the Java version that is required. Java 7 is not supported. For installation instructions, see Installing Integration Composer. IBM Endpoint Manager Version 9.0 or later For information about installing IBM Endpoint Manager, see the IBM Endpoint Manager Installation Guide. Ensure that the Client Configuration dashboard and the Manage Distribution Packages dashboard are set up. For instructions, see the Software Distribution User's Guide for IBM Endpoint Manager for Lifecycle Management. 6

7 3. Downloading and installing the package To install the PMP packages using the Process Solution Installer, complete the following steps: 1. Download the PMP.zip file from the ISM library. 2. From the administrative server, run the Process Solution Installer. You can find the installer at the following locations: On Windows systems: c:\ibm\smp\bin\solutioninstallergui.bat On Linux systems: /opt/ibm/smp/bin/solutioninstallergui.sh To install the IBM_Endpoint_Manager_Software_Distribution.zip package, use the ISM Content Installer application in IBM Control Desk. For more information about using the application, see Content Installer application in the IBM Control Desk Knowledge Center. 7

8 4. Importing data from Endpoint Manager into Control Desk This section of the guide explains how to import data from Endpoint Manager into Control Desk using Integration Composer. To import data, complete the following steps: 1. Log in to Integration Composer. 2. To define a data source for Control Desk, complete the following steps: a) On the main Integration Composer page, select Define a New Data Source. b) On the Data Schema tab select Deployed Asset 7.5 and click Next. c) In the Data Source field on the Data Source tab, enter sccd-dpa and click Next. d) In the Connection Information window, enter values in the fields as shown in the following image and click Finish. 8

9 3. 4. To define a data source for Endpoint Manager, complete the following steps: a) On the main Integration Composer page, select Define a New Data Source. b) On the Data Schema tab select IBM Endpoint Manager 9.0 and click Next. c) In the Data Source field on the Data Source tab, enter iem90-dpa and click Next. d) In the Connection Method field on the Connection Information tab, select IBM Endpoint Manager SUA API and specify a user name and password, as shown in the following sample image: e) Click Finish. To define a mapping from the Endpoint Manager to Control Desk integration, complete the following steps: a) On the main Integration Composer page, select Create New Mapping. 9

10 b) In the New Mapping window, select the following values: Source: iem90-dpa Target: sccd-dpa Mapping Name: iem90-dpa-sccd c) Click OK. d) On the Connection Information tab for Endpoint Manager, enter the Endpoint Manager password and click Finish. e) On the Connection Information tab for Control Desk, enter the Maximo database password, and click Finish. 10

11 Integration Composer displays the Mapping window. f) In the Mapping window, click Select Action and choose Import. g) In the Import Mapping window, select IEM90ToDPA75.fsn and click Open. h) From the Select Action menu, choose Save. i) From the Select Action menu, choose Close. j) Click Yes to save the mapping. 11

12 5. To execute the mapping to import data from Endpoint Manager to Control Desk, complete the following steps: a) Open a command prompt. b) Go to the bin directory in your Integration Composer installation directory. c) Run the executemapping script as shown in the following example. executemapping.bat <mapping_name> <maximo_id> <maximo_passwd> <iem_id> <iem_passwd> <maximo_id> <maximo_passwd> For example: C:\Integration Composer\bin>executeMapping.bat iem90-dpa-sccd maximo 123** User_id 567*** maximo 123** Output should be similar to the following sample: Verify that there are no errors. 12

13 5. Importing data from Software Knowledge Base Toolkit into Control Desk (optional) This section of the guide explains how to import data from Software Knowledge Base Toolkit into Control Desk. Importing the software catalog is optional. You can manually create records in the Software Catalog application if the imported data does not contain the software records that you need. To importing the software catalog there are two tasks that you need to perform: Download the software catalog file Configure the cron task that schedules and runs the import Download the software catalog file: The first step is to download the latest software catalog file. IBM publishes software catalog data provided by Software Knowledge Base Toolkit on the following IBM site: ftp://ftp.software.ibm.com/software/tivoli_support/misc/cando/tivolicatalog/ibm/swkbt/ The file is updated monthly. The name of the file to download is IBMSoftwareCatalog_canonical_form_yyyymmdd.zip where yyyymmdd is the date code for the date that the file was released. It is updated at the beginning of a month and contains the catalog through the end of the previous month. Inside the zip file is an XML file (similarly named). This is the file that is needed on the Maximo server. Download the file from the ftp site and copy the XML file to a directory, for example c:\swkbt. Configuring a cron task to import the software catalog: After you download the software catalog file, complete the following steps to configure the cron task to import the data into Control Desk: 1. Log in to Control Desk and select Go To > System Configuration > Platform Configuration > Cron Task Setup. 2. In the Cron Task Setup application, select SWCATALOGIMPORT, the cron task for software catalog imports. 3. In the Cron Tasks Instances table on the Cron Task tab, expand the row for the Software Knowledge Base Toolkit cron task instance. 4. In the Schedule field, click Set Schedule and specify a schedule for importing software catalog data from the Software Knowledge Base Toolkit. Since this file will only be imported once, you can set the interval to a small interval to get the import process going. You can disable the cron task instance after the import is complete. 5. To activate the schedule, select the Active check box. 6. On the Parameters sub tab, expand the row for the PARTIALRUN parameter and specify 6 in the Value field. 7. Expand the row for the REPOSITTORYID parameter. In the Value field, specify the databaseinstanceid attribute that is in the header element in the XML file that you imported. 13

14 8. Expand the row for the TEMPDIR parameter. In the Value field, specify the directory where the XML file is located. 9. Expand the row for the TEMPFILE parameter. In the Value field, specify the name of the temporary file for the software catalog. Typically, you rename the XML file to name that is shorter than the original name. 10. Save the cron task. 14

15 6. Setting up the Jython library Control Desk ships the jython.jar that contains the Jython modules needed (such as httplib). The jython.jar can be found under the <install-dir>/maximo/applications/maximo/lib/ directory. For example: C:\ibm\SMP\maximo\applications\maximo\lib. Extract the jython.jar into a directory on the server, for example: C:\jython directory. (If using in a clustered environment, extract the jython.jar to the same location on all the nodes and set the system property to point to that location.) Set the path according to where it was extracted to on the Control Desk server. If you extract the jython.jar to another location (for example, if you are using Linux), you will need to change the path to the Jython library in the system property as follows: go to System Properties application, and look for the property pmsc.iem.jythonlib, and set the correct path. 15

16 7. Promoting deployed asset data to authorized assets Before you can provision software, you must promote the deployed asset data that you imported into Control Desk to authorized assets. NOTE: Before you begin this step, make sure that you specified a top-level IT asset classification and that the default insert site is set for the administrator (maxadmin in our sample). Otherwise, the next step will fail. For information about specifying a top-level asset, see Specify a top-level class for IT assets and software in the IBM Control Desk Knowledge Center. A default insert site can be specified in the Users application in the Security module. Also, test to make sure you can create a new record in the Assets application. For information about promoting deployed assets, see Promotion to assets. To promote deployed assets, complete the following steps: 1. In Control Desk, Go To >Assets->Deployed Assets->Computers. 2. Select the computer that you want to promote, in this case a computer that has Endpoint Manager. 3. From the More Actions menu, select Promote to Asset. 4. In the Promote to Assets window, specify a site, classification, and status for the asset. 5. Click Apply Defaults. 6. Click OK. 16

17 8. Integrating Control Desk with IBM Endpoint Manager This section of the guide explains how to configure IBM Control Desk to connect with IBM Endpoint Manager. To integrate Control Desk with Endpoint Manager, you specify an end point for connecting to the Endpoint Manager server as follows: 1. Log in to Control Desk and select Go > Integration > End Points. 2. Under More Actions select Configure Endpoint Manager. The following window is displayed: 3. Specify a description for the Endpoint Manager server, and host name and port. 4. Enter the Endpoint Manager server credentials. 5. Click Test to verify the connectivity. 6. Click Save to store the connection data. 7. Import the Endpoint Manager certificate into the WebSphere Application Server (if your Administrator has not already done so) by entering the WebSphere Application Server credentials and specifying the node where the application server is running (the default server is MXServer). At the end of the configuration steps, the end point IEMSWDSERVER entry is created in the Control Desk database. 17

18 9. Creating Software Offerings for your Enterprise App Store This section of the guide explains how to create software offerings for your Enterprise App Store that can be deployed by Endpoint Manager. To create software offerings for an enterprise app store,create and publish software offerings using the publishing features that are added to the Software Catalog application You can use the following wizard to create software offerings for your Enterprise App Store. Users can then select the new software offerings in the Self Service Portal, and Endpoint Manager deploys the software to the user's computer. To publish the software on the Self Service Portal or to create your software offering, complete the following steps: 1. Log in to Control Desk and select Go To Applications > Administration > Deployed Assets > Software Catalog. 2. Select the software you want to deploy by clicking Software Name. 3. Under More Actions select Publish to Self Service. The following window is displayed: 4. In the Endpoint Manager Task section, select the double arrow next to the Task Name field to assign an Endpoint Manager task name. The following options are available: Assign from Software Package to assign a task by selecting a software package from Endpoint Manager. 18

19 Assign generic task to assign a task by selecting a Fixlet from Endpoint Manager. 5. To assign a task by selecting the software to be assigned, select Assign from Software Package and select the software package. 19

20 After you select the software package, click Next, specify the Endpoint Manager task to run, and click Assign: 20

21 6. To assign a task by selecting the Fixlet to run, select Assign generic task, select a task and click Assign: 21

22 7. After the deployment task is assigned, click Next. The following window is displayed: 8. In the Assign License section, select the double arrow next to the License field to assign a license. You can choose one of the following options: Select value to assign a predefined license. Go to Licenses to assign a new license. 22

23 After you assign a license, the following window is displayed: 9. If you want to publish the software only, select Publish the software. The software can be used in the IEM service offerings: Deploy Licensed Software to Multiple Assets and Deploy Multiple Licensed Software to a Single Asset. 10.If you want to publish the software and create a single offering for the selected software in the Self Service Portal, select Create a new offering and publish the software in the Self Service Center using that offering. The software is configured and is ready to be included in an offering. The offering can be deployed using Endpoint Manager. 11.You must specify the offering name and description, then click Configure to assign an image, a price book and a catalog for the offering. 23

24 When you click Configure, the following window is displayed containing three tabs: In the 'Catalog' tab you can assign an image and a catalog to the offering. In the 'Approval Process' tab you can change the Approval process or select your own workflow. 24

25 In the 'Price and Cost' tab you can select the price book and specify the offering price and the license allocation. Note: In the Price Book list you can only see the price books in draft status. To see the price in the offering, you must activate it from the Price Book application. The price book is then added to the Price Book list starting from the revision date. 12.Click Finish. Verifying the integration After you complete the steps in this guide, you can request the software, and it will be installed on the computer that you specified. To verify that the integration works properly, go to the Self Service Center and select the software offering. Then check that the offering was deployed on the computer as expected. 25

26 10. Deploying licensed software to assets This section of the guide explains how to use the features provided in the content package to deploy licensed software to assets: IBM_Endpoint_Manager_Software_Distribution.zip. The content installer package contains three new Service Offerings and an Automation Script as part of the PMP package (iem_swd_base.zip). You can use the new offerings that are included in the package to perform the following tasks: deploy licensed software to multiple assets deploy one or more licensed software products to a single asset deploy licensed software when you reimage an asset After installing the content package, you can access the offerings, from the Self Service Center under Services > IEM Software Deployment. Note: The software that you want to deploy by using these offerings is software that you published using the steps described in Creating Software Offerings for your Enterprise App Store on page on page Prerequisite Before you use the offerings that are provided in this package, ensure that you create software offerings that you want to deploy using the steps described in Creating Software Offerings for your Enterprise App Store on page 18. Complete all steps that are listed in the Integrating Control Desk with Endpoint Manager chapter on page 17. In the Creating a software offering for your Enterprise App Store chapter that begins on page 18, complete only steps 1 through 9. Do not assign licenses. License assignment is handled by the offerings that are described in the following sections of this chapter. 26

27 10.2 Deploy Licensed Software to Multiple Assets With this offering you can deploy a licensed software package to one or more assets. The offering window is shown below: In the Software Name look-up field, specify the software to deploy, then select the asset(s) that require the software. Assets should be in Operating or Active status and must belong to the hierarchy of the top-level IT asset class. The look-up lists only software with a license associated. The site id of the asset should be associated with the organization of the license for the software. If the software is associated with more than one license, then a default license should be specified for that software; otherwise, it cannot be used for deploying the software. A default license can be specified in the Default License field under the Licenses tab as shown below: 27

28 When you click Submit Request on the offering, a workflow checks whether there are enough licenses available. If there are enough licenses available, it reserves a license for each asset, and initiates the IEM action to deploy the software. If there are not enough licenses available, an inbox assignment is created and it is assigned to the license administrator person group (IEMLICM) to procure more licenses. By default, maxadmin user is a member of the IEMLICM person group. The escalation periodically checks the status of the action and updates the status. The deployment status can be viewed in the Deployment Status tab on the Service Request as shown in the following example: 28

29 Clicking on the Log tab displays information about the deployment status: If there are problems with the software deployment, for example, unable to check the status of deployment or unable to allocate license, an Inbox assignment is created for the task owner group (IEMTSKGR). By default, maxadmin user is a member of that group also. 29

30 10.3 Deploy Multiple Licensed Software to a Single Asset This offering allows you to deploy one or more licensed software packages to a single asset. The offering window is shown below: In the Asset field, specify the asset that requires the software to be deployed, then select one or more the software packages using the Select button. Assets should be in Operating or Active status and must belong to the hierarchy of the top-level IT asset class. The site id of the asset should be associated with the organization of the license for the software. If the software is associated with more than one license, then a default license should be specified for that software; otherwise, it cannot be used for deploying the software. A default license can be specified in the Default License field under the Licenses tab as before. Upon submitting the offering, a workflow checks whether there are enough licenses available, and if there are not enough licenses available, an Inbox assignment is created for the license administrator to procure more licenses. If there are enough licenses available, it reserves the licenses for the asset, and initiates the IEM action to deploy the software. The escalation periodically checks the status of the action and updates the status. The deployment status can be viewed in the Deployment Status tab on the Service Request as shown in the previous offering. 30

31 10.4 Re-image an Asset This offering is used for re-imaging an asset with the licensed software that was allocated to the before re-imaging. In the Asset field, specify the asset that needs to be re-imaged, and click Submit Request. A workflow checks for the software licenses that were allocated to the selected asset, and redeploys the software to the asset using Endpoint Manager. No Inbox assignment is created since the license is already allocated to the asset. The status of the deployment is updated in the Deployment Status tab on the Service Request. 31

32 10.5 De-allocate Licenses when Asset is Decommissioned This automation script enables you to de-allocate licenses associated with an asset when the status of the asset changes to Decommissioned. The Decommissioned status maps to a number of external statuses as shown in the following figure (BROKEN, DECOMMISSIONED, DISPOSED, INACTIVE, MISSING, SEALED): The Automation Script is called IEMSWDASSETDECOM. The script checks whether the Internal Value for the asset is set to DECOMMISSIONED and de-allocates the licenses associated with the asset. The script is invoked automatically when the internal value of the status of the asset changes to Decommissioned. 32

33 10.6 Troubleshooting Use the following hints and tips to ensure that your deployments work as needed or to troubleshoot problems that you encounter. 1. Make sure that the PSI package is installed using the solution installer command. You can verify this from the System Information. Look for: IBM Endpoint Manager Integration Enablement 2. Make sure that the content installer package is installed using the Content Installer application. You can verify this by going to the offerings application and searching for offerings that start with IEM. 3. Make sure that the SSL certificate of the IEM server is imported into WebSphere. This can be verified by logging on to WAS administrator console and going to SSL certificate and key management > Key stores and certificates > CellDefaultTrustStore > Signer certificates. Look for an entry for the IEM server host name and make sure that the certificate is valid and not expired. 4. Make sure that the end point is configured (updated with the correct URL, user_id and password). If you get an SSL handshake error, it could be due to the certificate not being imported properly, or the user_id and password is not correct, or firewall issues. 5. Make sure that the software that you are trying to deploy has the deployment task tab filled in with the IEM fixlet id (and, if the site is not the Master Action site, a siteid or sitename is required). You can verify this by going to the software catalog application and looking at the software that you are trying to deploy. 6. Make sure that the assets are deployed assets (promoted after importing from IEM). Otherwise, you will get the error: Unable to get the deployed asset for one or more assets specified. 7. Make sure that the escalation is activated. Otherwise, the deployment status will not be checked and the workflow will be active with an active assignment. 8. Make sure that the jython.jar is extracted into a directory on the server Fox example: C:\jython directory, or the property pmsc.iem.jythonlib is updated if a different directory is used. If not, you will get the error: nameerror: httplib not found. 9. If you experience errors when you submit the Offering, you can enable logging to help determine the problem. To do this, go to System Configuration > Platform Configuration > Logging. Set the log level of the Asset Management logger to DEBUG, and make sure the Active box is checked. Save the settings and click the Apply Settings action. Recreate the problem. Debugging details can be found in the application server's log file. 33

34 Appendix 1: Manual steps to integrate Control Desk with Endpoint Manager This section explains how to perform manual configurations for the various components in Control Desk for software provisioning. It is provided as a convenience if you choose not to use the automated features that are provided for configuring a connection to IBM Endpoint Manager and setting up IBM Control Desk for deployable software offerings. For each deployable software package, you provide deployment details such as Endpoint Manager FixletId or Task ID on the Deployment Tasks tab of the associated record in the Software Catalog application. You must configure an endpoint for connecting Control Desk to the Endpoint Manager server. Step 1: Specify an end point for connecting to the IEM server To specify an end point for connecting to the Endpoint Manager server, complete the following steps: 1. Log in to Control Desk and select Go To > Integration > End Points. 2. In the End Points application, select the IEMSWDSERVER end point. 3. In the Properties table, specify password, username, and URL (hostname and port) property values for connecting to the Endpoint Manager server. You can determine the URL by pointing to the Endpoint Manager URL; should display the list of sites. If you use this end point, you do not need to specify the end point name in the deployment task in the next step as this is the default endpoint name used. 34

35 Step 2: Create a software record in the Software Catalog This step describes how to add the software product to your Software Catalog. If you imported the software catalog from Software Knowledge Base Toolkit, the software record might already exist in the catalog and some of the steps in this section are not needed. You can skip steps 1 through 3. To add the software product to your catalog, complete the following steps: 1. In Control Desk, select Go To > Administration > Deployed Assets > Software Catalog. 2. Create a new item for the software that you want to deploy. 3. Optional: If you do not import the Software Knowledge Base Toolkit catalog, you might have to create a manufacturer record for the software in the Manufacturer Conversion application. The software catalog import from Software Knowledge Base Toolkit provides manufacturer records for most vendors. But if you do not import the catalog, you can create a manufacturer. a) To create a manufacturer, in the Manufacturer field in the Software Catalog application, click Go to Manufacturer Conversion. b) In the Target Manufacturer field of the Manufacturer Conversion application, specify a manufacturer for your software and select Yes in the Reviewed field. c) When you complete the manufacturer record, click Save and click Return With Value to return to the Software Catalog application. 4. In the Software Catalog application, you must add the Task ID that was assigned to the software when you created the software distribution task in Endpoint Manager to your software record. To add the distribution task ID to the software record, complete the following steps: a) Select the Deployment Tasks tab for the software product and click New Row to add deployment details for your software package. 35

36 b) In the Task ID field, enter the Task ID value from Endpoint Manager. Tip: One method of locating the Task ID is to open the Endpoint Manager Console, expand Tasks and Fixlets in the navigator, click Tasks Only, and search for your task. If the ID column does not display in the view, right-click in the heading area and select ID. c) In the Task Name field, enter a description for the task. d) In the Task Type field, select Install. e) In the Site ID field, enter the site ID or sitename. For Master Action Site, the site id and site name need not be filled in. Tip: To locate the Site ID, open the Endpoint Manager Console, click Sites in the navigator, and search for the task. If the ID column does not display, rightclick the heading area and select ID. Note: For Master Action Site, leave Site ID blank. f) In the Endpoint Name field, leave it blank if you want to use the default endpoint IEMSWDSERVER. Otherwise specify a different endpoint. Step 3: Import the Endpoint Manager server certificate into WebSphere Application Server Import the Endpoint Manager SSL certificate into the Control Desk WebSphere Application Server so that Control Desk can communicate with the Endpoint Manager server. To import the certificate, complete the following steps: 1. Log in to the WebSphere Application Server administrative console and click Security > SSL Certificate and key management > Key stores and certificates > CellDefaultTrustStore > Signer certificates > Retrieve from port, as shown in the following image. 36

37 2. Click Apply. 3. Click OK. Step 4: Create a license for the software In this step you create a license record for the software product that you are planning to deploy and associate it with the product. 1. In Control Desk, select Go To > Assets > Licenses. 2. Create a new license for the software product that you want to deploy, in this sample Adobe. 3. In the Associated Products section, associate the license with the software product. 37

38 4. To activate the item, in the Status field select Active. 5. Save the license. Step 5: Activate the escalation An escalation for the offering deployment is included in the optional Service Catalog content that was installed with Control Desk. The escalation polls Endpoint Manager to determine whether or not the deployment was successful and the software was installed on the computer. Activate the escalation to start the polling process. To activate the escalation, complete the following steps: 1. In Control Desk, select Go To > System Configuration > Platform Configuration > Escalations. 2. Select the IEMSWDSTATUS escalation. 3. Select the Activate/Deactivate Escalation action and make sure it is activated. By default is set to poll IEM server every 5 minutes for the status of the deployment. This can be adjusted according to your environment. Also, it polls for a maximum of 30 times at this interval. If the 38

39 maximum number of retries needs to be changed, it can be done in the Automation Scripts application. To do this go to the Automation Scripts application and filter IEMSWDTAKEACTION. There are two scripts: IEMSWDTAKEACTION and IEMSWDTAKEACTIONMULTISW. In the Variables tab there is a maxretry variable set to 30. This can be adjusted according to your environment for both of these scripts. Step 6: Verify the integration After you complete the steps in this guide, you can request the software, and it will be installed on the computer that you specified. To verify that the integration works properly, go to the Self Service Center and select the software offering. Then check that the offering was deployed on the computer as expected. 39

40 Copyright IBM Corporation 2014 IBM United States of America Produced in the United States of America US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PAPER AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes may be made periodically to the information herein; these changes may be incorporated in subsequent versions of the paper. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this paper at any time without notice. Any references in this document to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation 4205 South Miami Boulevard Research Triangle Park, NC U.S.A. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. If you are viewing this information softcopy, the photographs and color illustrations may not appear.

41 Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( or ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Other company, product, or service names may be trademarks or service marks of others.