Step 1: Defining your data source connections

Perform this task to define the data source connections used to linkIntegration Composer to data sources.

Before you begin

Integration Composer uses a JDBC driver or an API to connect to data sources. Before you can create a mapping (Step 2: Creating a mapping), you must have a data source connection defined for both the source (in this case, the discovery tool database) and the target, Deployed Assets 7.6 (the Maximo® database).

In this step, you define a data source by running either the defineDataSource.bat command (on Microsoft Windows operating systems), or the defineDataSource.sh command (on UNIX-based operating systems). You run the command from the bin subdirectory in your Integration Composer installation directory.

Before you run the command, review the following command syntax, option and parameter definitions, and usage:

Syntax:  
     
  defineDataSource  
    help
    listSchemas repositoryPwd
    listDataSources repositoryPwd

    repositoryPwd sourceName schemaName db2|mssql|inet|oracle hostname port sid|database sourceUser sourcePwd tableOwner1
    repositoryPwd sourceName schemaName generic driver url sourceUser sourcePwd tableOwner2
    repositoryPwd sourceName schemaName ccmdb hostname port sourceUser sourcePwd true|false trustedLocation3
    repositoryPwd sourceName schemaName iemsua url sourceUser sourcePwd 4
 
Syntax notes:

1 Use this command syntax with IBM® DB2®, Microsoft SQL, or Oracle connection types
2 Use this command syntax with a generic connection type
3 Use this command syntax with a CCMDB connection type
4 Use this command syntax with an IBM Endpoint Manager 9.0 REST API connection type or a IBM Endpoint Manager for Software Use Analysis 2.x REST API connection type.  This option is available starting in Control Desk 7.5.1.1 and higher.
     

Options:

  
 
help
Displays the command syntax.
listDataSources
Displays all data sources that were created in the Integration Composer repository database.
listSchemas
Lists the available data schemas that can be used to create the data source.
     

Parameters:

  
 
ccmdb
The method for connecting to the data source you are defining. In this case you are using the IBM Configuration Discovery and Tracking API as your connection type to connect to IBM Tivoli® Application Dependency Discovery Manager in Control Desk.
db2|mssql|inet|oracle
The method for connecting to the data source you are defining. Use one of the following parameters as your connection type:
  • db2, IBM DB2 JDBC Driver., for IBM DB2 database users
  • mssql, Microsoft SQL Driver for Microsoft SQL server users
  • inet, i-net OPTA JDBC Driver for Microsoft SQL Server users
  • oracle, Oracle JDBC Thin Driver for Oracle database users
driver
The JDBC driver for the connection. Specify the path to the driver class; for example: org.objectweb.cjdbc.driver.Driver.
generic
The method for connecting to the data source you are defining. In this case you are using the generic JDBC Driver as the connection type.
 
hostname
Host name for the data source; the data source is either the source discovery tool database or the target Maximo database; for example, mxserver.mylab.raleigh.ibm.com.
port
Host port for the data source; for example, 50000.
repositoryPwd
The login password for the Integration Composer repository (the repository is in the Maximo database, so use its password); for example, maximopwd.
schemaName
The name of the source data schema; for example, "Tivoli Application Dependency Discovery Manager 7.2". (The name in the example includes spaces and therefore must be enclosed in quotation marks.)
sid|database
Specify a value for one of the following parameters:
  • The sid variable (only for Oracle databases), which represents the session identifier for the host; that is, the database instance name, for example, TADDM1
  • The database variable, which represents the database name for the data source; for example, TADDM72DB
sourceName
The name for the data source that you are creating. It can be a data source for the discovered source data or for the target. For example, TADDM72 might represent the discovered source data in IBM Tivoli Application Dependency Discovery Manager 7.2. (The name is case sensitive.)
sourcePwd
The login password for the new data source you are creating; for example, sys1adminpwd. (Database users enter a database password.)
sourceUser
The login user name for the new data source you are creating; for example, sysadmin.
tableOwner
Data schema name or database schema owner; for example, db2admin.
true|false
Specify if you use Secure Sockets Layer (SSL), true or false.
trustedLocation
The fully-qualified path of the Secure Socket Layer (SSL) certificate file used to connect to a server such as the Configuration Discovery and Tracking Server, which is used by IBM Tivoli Application Dependency Discovery Manager forControl Desk.
 
url
URL address to access a database instance or the IBM Endpoint Manager 9.0 REST API or IBM Endpoint Manager for Software Use Analysis 2.x REST API. For example, to access a database instance, specify jdbc:inetdae7:myserver:1433?database=altiris60. To access the IBM Endpoint Manager 9.0 REST API, specify https://iem_server_hostname:52311. To access the IBM Endpoint Manager for Software Use Analysis 2.x REST API, specify https://tem_sua_server_hostname:8090.
Note: Support for the IBM Endpoint Manager 9.0 REST API and the IBM Endpoint Manager for Software Use Analysis 2.x REST API begins in Control Desk 7.5.1.1 and higher.
     

Usage:

  
 
  • Close Integration Composer before issuing the command.
  • Windows conventions are followed for specifying directory names and directory paths. UNIX users should replace each backslash (\) with a forward slash (/) in any Windows directory paths that include backward slashes.
  • UNIX users must specify ./defineDataSource.sh as the command name; Windows users specify defineDataSource.
  • Issue the command from the bin subdirectory in your Integration Composer installation directory, installation_dir\bin.
  • Always type the parameter values for your command in the same order as they appear in the command syntax.
  • Parameter values with one or more spaces must be enclosed in quotation marks (").
  • If you enter an incorrect user ID or password, the database driver returns an authentication error; for example, the DB2 driver returns: Connection authorization failure occurred. Reason: User ID or Password invalid.
  • If the property mxe.db.user in the fusion.properties file is commented out or missing, the following error is displayed: The mxe.db.user property is not set in the fusion.properties file. Make sure the properties file is configured correctly.
  • If you enter an invalid schema name, the following message is displayed: Data schema invalidSchemaName does not exist in the Tivoli Integration Composer repository.
  • If you enter a connection type that is not valid, the following message is displayed: Connection type connType is not supported.
  • If all required arguments are not entered, the command syntax is displayed.
  • If you attempt to create a data source that already exists, but is not already being used in a mapping, the old data source is deleted and the new one is created.
  • If you attempt to create a data source already being used in a mapping, the following message is displayed: Data source sourceName already exists and cannot be overwritten because it is being used in the following mappings. Create the data source with a different name or delete the mappings first.

About this task

After you define the connection parameters for your data sources, Integration Composer saves them in its repository and uses them whenever you attempt to connect to the data sources.

Note: Perform the following procedure twice: once for the source (the discovery tool database), and once for the target (Deployed Assets 7.6). In addition to any error messages you might receive on screen, the log file could have some additional, related information, such as trace and usage information.

The steps for defining the data source connections follow.

Procedure

  1. If Integration Composer is open, close the application.
  2. Open a command prompt.
  3. Navigate to the bin subdirectory in your Integration Composer installation directory, installation_dir\bin.
  4. On the command line, type one of the following commands and add the command options, parameters, and values you want:
      Windows: defineDataSource
      UNIX: ./defineDataSource.sh
  5. Press Enter to run the command.

Example

The following command example (for Windows operating systems) shows a command to define a data source for IBM Tivoli Application Dependency Discovery Manager 7.2 running on an IBM DB2 database:

defineDataSource maximopwd TADDM72 "Tivoli Application Dependency Discovery Manager 7.2" db2 mxserver.mylab.raleigh.ibm.com 50000 TADDM72DB sysadmin sys1adminpwd db2admin

On UNIX-based operating systems, specify ./defineDataSource.sh instead of defineDataSource as the command name.

Successful command processing yields the following message:

Data source TADDM72 saved successfully.

What to do next

Make sure you have performed this data source connection procedure for both the discovery tool database and Deployed Assets 7.6 (the Maximo database).

Then go to Step 2: Creating a mapping.

Parent topic: Using the Integration Composer command line interface

Feedback