Policy Distribution Administrators Guide: Optim Connector Configuration

Transcription

1 Policy Distribution Administrators Guide: Optim Connector Configuration

2 Policy Distribution Administrators Guide: Optim Connector Configuration This edition applies to version of IBM Atlas Suite (product numbers 5725-D75, 5725-D76, 5725-D77) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2004, US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents 1 Introduction Installation and Configuration Connector Info... 5

4 1 Introduction This document tells you how to install and configure the Policy Distribution Connector for InfoSphere Optim. To use the instructions in this document you must have: An installed, working instance of InfoSphere Optim. An application server installed on the same machine that hosts Optim (for deploying the Connector). An installed, working instance of IBM Global Retention Policy and Schedule Management (part of IBM Atlas Suite). A network connection between the Optim host and the Atlas host. A copy of PolicyFederation601.zip, the archive that contains the Optim Connector. As part of the Connector configuration, you must log into Atlas and create and configure a Data Source. If you re unfamiliar with Data Sources, see these users guides: IBM Atlas Users Guide: Data Source Definition IBM Atlas Users Guide: Data Source Maintenance with IIM IBM Atlas Users Guide: Data Source Maintenance without IIM

5 2 Installation and Configuration To install and configure the Optim connector, you first log into the Connector s host machine and do the following: 1 Open PolicyFederation601.zip and go to the PolicyFederation/connectors/pd_connector directory. 2 Deploy the pd-connector.war file (within pd_connector) in the application server on the Optim host. 3 Open the authentication.properties file and set the username and password parameters to whatever values you want; you ll be asked to supply these values when you configure the Data Source in Atlas. 4 Save and close authentication.properties. 5 Copy the authentication.properties file you just modified into a directory that s in the application s classpath. The rest of the steps are performed from the Atlas application: 1 Log into Atlas as a user who can create, modify, and approve Data Sources. 2 Create a Data Source that will represent Optim. You can define the Data Source as desired, but make sure you check the Manage Policy Distribution checkbox. Note that the set of fields that are required depends on how your system is configured. 3 Approve the new Data Source. 4 Go to the Data Source s Policy Distribution tab, select the Setup subtab, and set the following attributes: Vendor. Select External Connector Connector Info. This is a series of key/value properties that tells the Connector how to interact with Optim, as explained in Connector Info, below. Connector URL. The URL, port, and location of the Connector in this form: Username and Password. Use the values you supplied in the authentication.properties file. 5 Click Save. You should see a success message. The Connector should now be ready to be used. 2.1 Connector Info The Connector Info field on the Policy Distribution > Setup page takes a series of semicolon-separated key/value properties, where each property is in the form key=value. For example: commandlocation=c:\program Files\optim\rt\bin; input=c:\optim\pss\stream1\import.xml; directory=xyz; preserveimportfile=false

6 Installation and Configuration Policy Distribution Administrators Guide: Optim Connector Configuration The keys and the values they take are listed below. I M P O R T A N T The pathnames that you provide to the commandlocation and input parameters live on the Optim server, and are specified as they are known to the Optim server s file system. commandlocation is the full pathname of Optim s bin directory. input is the full pathname of the import.xml file that describes the policies that need to be distributed, and that Atlas sends to the Connector. The path to the file (c:\optim\pss\stream1 in our example) must already exist the Connector doesn t create it for you. The file itself (import.xml) must not exist; the Connector won t overwrite the file if it exists. directory (optional) is an Optim Directory in which Optim stores the policies that it reads in the import.xml file. You create the Directory through the Optim configuration tools. Note that this isn t a file system designation you don t supply a full pathname. If you don t supply a directory value, Optim applies the policies without storing them. preserveimportfile (optional), if true, tells the Connector to delete the import.xml file after the file has been read. If false, the file isn t deleted. In a production system, you would always set this to true; as mentioned above, the Connector won t overwrite the file if it already exists. When you re debugging, you may want to preserve the import file for examination, and then delete the file by hand before the next policy propagation. The default is true (the import file is deleted after it has been read). 6