Skip Headers
Oracle® Enterprise Manager Installation and Configuration Guide for IBM Tivoli Enterprise Console Connector
Release 1.0.4.1.0

E14038-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 Installing the Connector

The Oracle Enterprise Manager Connector Framework requires a web service interface for exchanging event information with IBM TEC. Since TEC does not provide a web services interface, you must install a third-party TEC web service front-end, which is included in the Oracle Enterprise Manager installation package.

You can install the web service on any Unix or Windows system that has connectivity with the TEC server. In addition to the TEC web service front-end, you must also install a back-end TEC Agent on the same physical system as the TEC server. The TEC Agent is preconfigured and is also included in the Oracle Enterprise Manager installation package.

Figure 2–1 shows the communication between the various components of the TEC Connector.

Figure 2-1 Connector Communication Between Components

Flowchart shows connections between EM and IBM TEC

The following sections in this chapter discuss these topics:

Installation Platforms

You can install the TEC web service on the following platforms that support Java JRE 1.6:

You can install the TEC Agent on the following platforms:

Installing the IBM TEC Web Service

The TEC web service acts as a front-end for all data flowing into and out of TEC. Oracle Enterprise Manager posts calls to the web service whenever it needs to create or update an event, or get new or updated events from TEC.

You can install the TEC web service on any Unix or Windows system that has connectivity to the TEC server and the Oracle Enterprise Manager server.

Installing and Running the IBM TEC Web Service on Unix

The following sections explain how to install and then subsequently run the Web Service.

Installing the Web Service on Unix

To install the web service on a Unix platform, perform the following steps:

  1. Create a directory where you want to install the web service.

  2. Open a terminal and change the working directory to the installation directory.

  3. Download tec_connector_bundle.jar from the Oracle Technology Network to the installation directory, then extract the component .jar files.

  4. Make sure the JAVA_HOME environment variable is set to the directory where Java 1.6 is installed.

  5. Enter the following command to unzip and extract the .tar file:

    $JAVA_HOME/bin/jar xvf TEC_webservices_adapter.jar

    This creates the adapters directory that contains the installation files.

    Note:

    If the system where the TEC web service is being installed does not have the JDK installed, you cannot extract the jar file contents. You need to copy the jar file to a system that has the JDK installed and transfer the files after they have been extracted.
  6. Enter the following command to change the working directory:

    cd adapters/endpoints/tec

  7. Enter the following command to run the installation script:

    sh ./install.sh

  8. When the script prompts whether you want to use HTTPS:

    • If you specify Y, the web service is set up to use HTTPS port number 8443.

    • If you specify N, the web service is set up to use HTTP port number 8080.

  9. When the script prompts for the user name of the web service, enter the user name that must be provided to access the web service, or accept the default of "tec."

  10. When the script prompts for the password of the web service, enter the password that must be provided to access the web service, or accept the default of "webservice."

  11. When the script prompts for the host name of the IBM TEC server, enter the host name or IP address where the server is installed.

  12. When the script prompts for the port number of the IBM TEC server, enter the port number of the TEC reception port if a port mapper is not defined for the server. If a port mapper is defined for the server, specify a port number of 0.

    Note:

    The TEC reception port is defined by the tec_recv_agent_port parameter in the .tec_config file in the $BINDIR/TME/TEC directory.
  13. Copy the API jar files from the TEC installation disk to the adapters/lib/adapters directory. The files you need to copy are log.jar and evd.jar, which are located in the EIFSDK/jars directory of the TEC installation disk.

  14. If the web service was configured to run using the HTTPS protocol, you must install a SSL certificate. You can install a self-signed certificate, or you can acquire a certificate from a Certificate Authority (CA).

    • To generate and install a self-signed SSL certificate, enter the following commands, and replace <hostname> with the system host name or IP address that the TEC web service will use:

      "%JAVA_HOME%\bin\keytool" –delete -alias iwave -keypass iwavepw -storepass iwavepw -keystore keystore.jks

      "%JAVA_HOME%\bin\keytool" -genkey -alias iwave -keyalg RSA -keysize 1024 -dname "CN=<hostname>, OU=Development, O=iWave Software, L=Frisco, ST=TX, C=US" -keypass iwavepw -storepass iwavepw -keystore keystore.jks

    • To install a certificate that the Certificate Authority issues:

      • Request a certificate from a Certificate Authority, such as VeriSign.

        In the certificate request, make sure to specify the host name or IP address that the TEC web service will use. The host name in the certificate must match the host name configured for the web service. If they do not match, the web service cannot function.

      • After you obtain the certificate from the Certificate Authority, enter the following command to install the certificate, where <certificateFile> is the full path name of the file provided by the Certificate Authority:

        "%JAVA_HOME%\bin\keytool" -export -alias iwave -file <certificateFile> -keypass iwavepw -storepass iwavepw -keystore keystore.jks

The web service framework is now installed and ready to start.

Running the Web Service on Unix

To run the IBM TEC Web Service framework commands listed with the following tasks, first change the working directory to ...

adapters/bin

... in the installation directory.

  • Start — ./service.sh start

  • Shut Down — ./service.sh stop

  • Restart — ./service.sh restart

  • Check Status — ./service.sh status

Testing the Web Service on Unix

Perform the following steps to verify that the IBM TEC Web Service is functional.

  1. Open a terminal and change the working directory to the adapters/bin directory in the installation directory.

  2. Enter the following command to run the test script:

    ./testAdapter.sh

  3. If the test completes successfully, the last line the utility displays is "Test completed successfully."

    Note:

    If the HTTPS protocol is being used, the test fails if the installed JRE version is 1.6_10. An issue with this version causes the test to fail. To test the web service, you need to verify that you can load the WSDL in a web browser. See Section 3.3, "Testing the IBM TEC Connector".

Installing and Running the IBM TEC Web Service on Windows

The following sections explain how to install and then subsequently run the Web Service.

Installing the Web Service on Windows

To install the web service on a Windows platform, perform the following steps:

  1. Create a directory where you want to install the web service.

  2. Open a terminal and change the working directory to the installation directory.

  3. Download tec_connector_bundle.jar from the Oracle Technology Network to the installation directory, then extract the component .jar files.

  4. Make sure the JAVA_HOME environment variable is set to the directory where Java 1.6 is installed.

  5. Enter the following command to unzip and extract the .jar file:

    %JAVA_HOME%\bin\jar xvf TEC_webservices_adapter.jar

    This creates the adapters directory that contains the installation files.

    Note:

    If the system where the TEC web service is being installed does not have the JDK installed, you cannot extract the jar file contents. You need to copy the jar file to a system that has the JDK installed and transfer the files after they have been extracted.
  6. Enter the following command to change the working directory:

    cd adapters\endpoints\tec

  7. Enter the following command to run the installation script:

    .\install.bat

  8. When the script prompts whether you want to use HTTPS:

    • If you specify Y, the web service is set up to use HTTPS port number 8443.

    • If you specify N, the web service is set up to use HTTP port number 8080.

  9. When the script prompts for the user name of the web service, enter the user name that must be provided to access the web service, or accept the default of "tec."

  10. When the script prompts for the password of the web service, enter the password that must be provided to access the web service, or accept the default of "webservice."

  11. When the script prompts for the host name of the IBM TEC server, enter the host name or IP address where the server is installed.

  12. When the script prompts for the port number of the IBM TEC server, enter the port number of the TEC reception port. The default value for this port is 5529.

    Note:

    The TEC reception port is defined by the tec_recv_agent_port parameter in the .tec_config file in the $BINDIR/TME/TEC directory.
  13. Copy the API jar files from the TEC installation disk to the adapters\lib\adapters directory. The files you need to copy are log.jar and evd.jar, which are located in the EIFSDK\jars directory of the TEC installation disk.

  14. If the web service was configured to run using the HTTPS protocol, you must install a SSL certificate. You can install a self-signed certificate, or you can acquire a certificate from a Certificate Authority (CA).

    • To generate and install a self-signed SSL certificate, enter the following commands, and replace <hostname> with the system host name or IP address that the TEC web service will use:

      "%JAVA_HOME%\bin\keytool" –delete -alias iwave -keypass iwavepw -storepass iwavepw -keystore keystore.jks

      "%JAVA_HOME%\bin\keytool" -genkey -alias iwave -keyalg RSA -keysize 1024 -dname "CN=<hostname>, OU=Development, O=iWave Software, L=Frisco, ST=TX, C=US" -keypass iwavepw -storepass iwavepw -keystore keystore.jks

    • To install a certificate that the Certificate Authority issues:

      • Request a certificate from a Certificate Authority, such as VeriSign.

        In the certificate request, make sure to specify the host name or IP address that the TEC web service will use. The host name in the certificate must match the host name configured for the web service. If they do not match, the web service cannot function.

      • After you obtain the certificate from the Certificate Authority, enter the following command to install the certificate, where <certificateFile> is the full path name of the file provided by the Certificate Authority:

        "%JAVA_HOME%\bin\keytool" -export -alias iwave -file <certificateFile> -keypass iwavepw -storepass iwavepw -keystore keystore.jks

The following steps are optional. If you want the web service to run as a Windows service, perform the following steps.

  1. Enter the following command to change the working directory to the bin directory:

    cd ..\..\bin

  2. Enter the following command to install the web service as a Windows service:

    service.bat install

The web service framework is now installed and ready to start.

If the Microsoft SCOM Web Service was configured to use the HTTPS protocol, the certificate must be imported into Enterprise Manager. See Section 2.2.3, "Adding Signed Certificates to Enterprise Manager" for instructions.

Running the Web Service on Windows

Standalone Service

To start the TEC web service framework when set up as a standalone application (not set up to run as a Windows service):

  1. Change the working directory to the adapters\bin directory in the installation directory.

  2. Run the following command:

    startAdapters.bat

To shut down the TEC web service framework, close the window where you started the adapter.

Windows Service

To start the TEC web service framework when set up to run as a Windows service:

net start iWaveAdapters

To shut down the TEC web service framework:

net stop iWaveAdapters

Testing the Web Service on Windows

Perform the following steps to verify that the IBM TEC Web Service is functional.

  1. Open a terminal and change the working directory to the adapters/bin directory in the installation directory.

  2. Enter the following command to run the test script:

    ./testAdapter.bat

  3. If the test completes successfully, the last line the utility displays is "Test completed successfully."

    Note:

    If the HTTPS protocol is being used, the test fails if the installed JRE version is 1.6_10. An issue with this version causes the test to fail. To test the web service, you need to verify that you can load the WSDL in a web browser. See Section 3.3, "Testing the IBM TEC Connector".

Adding Signed Certificates to Enterprise Manager

The Service Manager SSL certificate must be imported into Enterprise Manager. For versions 10.2.0.4 and 10.2.0.5, perform the steps in Section 2.2.3.1, "Adding Signed Certificates to Wallet Manager". For versions 11.1.0.1, perform the steps in the Adding Signed Certificates to cacerts section.

Adding Signed Certificates to Wallet Manager

Note:

Oracle Wallet Manager is available at $ORACLE_HOME/bin on OMS for versions 10.2.0.4 and 10.2.0.5. See the Oracle Application Server Administrator's Guide for details.

Perform the following steps in Oracle Enterprise Manager to add signed certificates:

  1. Do the following to obtain a copy of the certificate that the TEC web service is using:

    1. Open a command prompt window and change the working directory to ...

      <TECWS_INSTALL>/adapters/conf

      ... where <TECWS_INSTALL> is the directory where the TEC web service is installed.

    2. Issue the following command to extract the certificate:

      — Unix platforms:

      $JAVA_HOME/bin/keytool -exportcert -alias iwave -file TECws.cer -keystore keystore.jks -storepass iwavepw

      — Windows platforms:

      "%JAVA_HOME%\bin\keytool" -exportcert -alias iwave -file TECws.cer -keystore keystore.jks -storepass iwavepw

    3. Transfer the certificate file TECws.cer to the system where Enterprise Manager is installed.

  2. Open a new terminal and set the ORACLE_HOME environment variable to the directory where OMS is installed.

  3. As Super Administrator, create a wallet using the following orapki utility command at the OMS host:

    $OMS_HOME/bin/orapki wallet create -wallet client -auto_login

  4. Add the trusted certificate to the wallet by entering the following command:

    $OMS_HOME/bin/orapki wallet add -wallet client -trusted_cert -cert <certFile>

  5. To view the content of the wallet, enter the following command:

    $OMS_HOME/bin/orapki wallet display -wallet client

    Verify that the certificate that was added is listed in the Trusted Certificates.

  6. Start Oracle Wallet Manager and open the client wallet.

    Note:

    Oracle Wallet Manager is available at $OMS_HOME/bin. See the Oracle Application Server Administrator's Guide for details.
  7. Click on Trusted Certificates and select Operations on the main menu.

  8. Select Export All Trusted Certificates.

  9. Save the file as certdb.txt.

  10. Place the file certdb.txt in the connector home root directory ($OMS_HOME/sysman/connector).

    If the certdb.txt file already exists in the root directory, open the file and add the contents of your certdb.txt file to the existing content.

Java SSL can now use this file for communication between Oracle Enterprise Manager and the TEC web service in HTTPS mode.

See Also:

For additional information on creating a wallet, see "Creating and Viewing Oracle Wallets with orapki" in the Oracle Database Advanced Security Administrator's Guide, 10g Release 2 (10.2).

Adding Signed Certificates to cacerts

Do the following in Enterprise Manager to add signed certificates to the Java cacerts keystore:

  1. Copy the certificate to the Enterprise Manager server system.

  2. Determine the location of the JRE in the Oracle Home directory.

  3. Open a command window and navigate to the JRE bin directory.

  4. Enter the following command to add the certificate to the cacerts keystore:

    keytool -importcert -keystore ..\lib\security\cacerts -storepass changeit -trustcacerts -file <certfile> -alias scomws_cert
    
  5. Restart OMS by opening a command window, changing the working directory to <ORACLE_HOME>/oms10g/bin, and issuing the following commands:

    emctl stop oms
    emctl start oms
    

Oracle Enterprise Manager Event Polling to TEC

After installation and configuration, the event connector automatically polls the TEC web service for events to exchange alerts and events with Oracle Enterprise Manager. The poll cycle is configurable, where the duration is specified in minutes with a minimum possible duration of 5 minutes.

Every poll cycle, the event connector polls for up to (40 * polling interval) new or updated events in TEC. The Oracle Enterprise Manager connector framework processes and acknowledges all of the events provided in the poll response.

Installing and Running the IBM TEC Agent

The following sections provide procedures for installing and running the TEC Agent.

Installing the Agent

The back-end TEC Agent pushes data from TEC into the TEC Web Service. The Agent is comprised of a script (invoked by TEC rules and a command line utility invoked by the script) to send a transaction to the TEC Web Service. The TEC Agent must be installed on the same physical system as the TEC server. The TEC Agent is preconfigured to interface with the TEC Web Service and requires minimal configuration.

To install the TEC Agent, perform the following steps:

  1. Download tec_connector_bundle.jar from Oracle Technology Network, extract the components, and put the appropriate installation file into the directory where you intend to install the TEC Agent.

    Note:

    You need to do this on the IBM TEC system host.

    Table 2–1 identifies the installation file name for each supported platform.

    Table 2-1 Platform Installation Files

    Platform Installation File

    IBM AIX

    TECAgentAIX.tar.gz

    Sun Solaris

    TECAgentSolaris.tar.gz

    Microsoft Windows

    TECAgentWindows.zip


  2. Open a terminal and change the working directory to the installation directory.

  3. Unzip the installation file. This creates the TEC-agent directory that contains the installation files.

    • For Windows platforms, use a zip utility to unzip the TECAgentWindows.zip file.

    • For AIX platforms, issue the following commands to unzip and untar the files:

      gunzip TECAgentAIX.tar.gz

      tar xvf TECAgentAIX.tar

    • For Solaris platforms, issue the following commands to unzip and untar the files:

      gunzip TECAgentSolaris.tar.gz

      tar xvf TECAgentSolaris.tar

  4. Set up the TEC environment:

    • For Windows systems, enter the following commands to start the bash shell:

      %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

      bash

    • For Unix systems, enter the following command to start the bash shell:

      /etc/Tivoli/setup_env.sh

  5. Change the working directory to the TEC-agent directory.

  6. Enter the following command to run the setup script to configure the TEC Agent:

    ./install.sh

    The following prompts appear in this sequence:

    • Enter the hostname or IP address where the TEC adapter is installed [localhost]:

      Enter the host name or IP address of the system where the TEC Web Service adapter is installed.

    • Do you want to install the default Oracle Enterprise Manager classes and rules [Y]?

      Enter Y to install and activate the class definitions and rules for the OracleEnterpriseManager class. This class must be installed before alerts from Enterprise Manager can be inserted into TEC. Enter N to skip the installation of the OracleEnterpriseManager class. The classes must be manually installed if you choose not to install the class definitions.

    The following prompts appear in this sequence if you choose to install the OracleEnterpriseManager class.

    • Enter the name of the rule base to use:

      Enter the name of the rule base where the class should be installed. This can be an existing rule base or one that does not exist.

    • Rule base could not be found. Do you want to create it [N]?

      This prompt only appears if the rule base specified in the previous response did not already exist. Specify Y to create a new rule base, or specify N to exit the script without installing the OracleEnterpriseManager class.

    • Enter the rule base directory:

      This prompt only appears if the script cannot determine the directory where the rule base files are located. Enter the directory where the rule base files are located. The script terminates if the directory does not exist.

  7. Delete the installation file from the installation directory.

Running and Stopping the Agent

You do not need to start or stop the Agent. A TEC rule invokes it whenever a transaction needs to be sent to the TEC Web Service adapter. The Agent terminates after the transaction has been successfully delivered to the TEC Web Service adapter.

Updates to TEC Rules

TEC rules must initiate event information sent from TEC to the TEC Web Service. This requires changes to the TEC rule sets to invoke the tec2uniagt script, which sends event information to the TEC Web Service. The following sections describe the required changes to the TEC rule sets for data flowing in both directions.

Handling Data Flowing from Enterprise Manager to TEC

For the TEC connector to work out of the box, the Oracle Enterprise Manager default classes must be installed and loaded into the TEC Server. When installing the TEC Agent, you have the option to install the classes and rules.

If you choose to install the default classes, the install script compiles the classes and rules, and loads them into the TEC Server. It also shuts down and restarts the server to pick up the new classes.

If you choose not to install the classes, you must manually install the classes and rules. The default class files are located in the TEC-agent/Samples directory. The OracleEnterpriseManager.baroc file defines the 5 classes that are required to insert events into TEC. The OracleEnterpriseManager.rls file contains the rules required to send the event data back to the TEC Web Service after an event has been created, updated, or closed. To manually install the classes with the install script, perform the following steps.

  1. Open a command terminal at the system where the TEC server is installed.

  2. Change the working directory to the TEC-agent/Samples directory in the TEC Agent install directory.

  3. Set up the TEC environment:

    • For Windows systems, enter the following commands to start the bash shell:

      %SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

      bash

    • For Unix systems, enter the following command to start the bash shell:

      /etc/Tivoli/setup_env.sh

  4. Enter the following command to install the default classes:

    ./rule_load.sh

Handling Data Flowing from TEC to Enterprise Manager

To send new/updated events from TEC to Enterprise Manager, you need to define one or more rules in TEC to call the tec2uniagt script. The script is named tec2uniagt.sh on Unix systems and it is named tec2uniagt.cmd on Windows systems. This script sends an event to the TEC Web Service and makes the event available for Enterprise Manager to consume.

You need to identify the classes that you want Enterprise Manager to consume. You also need to identify the conditions that should trigger sending an event to the TEC Web Service. An example of conditions would be changing the status or severity of an event. After you identify this information, you need to coordinate with the TEC Administrator to define and install the necessary rules to invoke the tec2uniagt script.

Sample files are provided in the TEC-agent/Samples directory of the TEC Agent install directory. The files are named tec2uniagt_sample.baroc and tec2uniagt_sample.rls. These files provide an example of how to invoke the tec2uniagt script and should not be installed on your TEC Server.

Installing the IBM TEC Connector in Oracle Enterprise Manager

The following procedure explains how to add the new TEC Connector.

Note:

Table 2–2 provides descriptions for the parameters shown for the emctl command in this procedure.

Note:

The commands in this section reference the OMS_HOME environment variable. OMS_HOME must be set to the OMS sub-directory in the Enterprise Manager installation directory. For versions 10.2.0.4 and 10.2.0.5, this is the oms10g directory. For version 11.1.0.1, this is the oms11g directory. Example settings of the OMS_HOME variable are /gc/OracleHomes/oms10g on a Unix platform running version 10.2.0.5, and C:\Oracle\Middleware2\oms11g on a Windows platform running version 11.1.0.1.
  1. Download the tec_connector_bundle.jar from the Oracle Technology Network to the installation directory, then extract the tec_connector.jar file.

  2. Enter the following command to extract the connector .jar file for versions 10.2.0.5 and 11.1.01:

    $OMS_HOME/bin/emctl extract_jar connector -jar <jarfile> -cname <connector_type_name>
    

    For version 10.2.0.4, enter the following command:

    $OMS_HOME/bin/emctl extract_jar connector <jarfile> <connector_type_name> <OracleHomes>
    

    Note:

    You should perform this extraction on all OMS instances, because all OMS instances need to access the files locally.

    Command Example

    $OMS_HOME/bin/emctl extract_jar connector -jar $OMS_HOME/sysman/ connector/tec_connector.jar" –cname "TEC Connector"
    

    When run, this creates a new connector subdirectory called TEC_Connector in the <OracleHomes>…sysman/connector directory.

  3. Register the connector by entering the following command based on the Enterprise Manager version, noting the required double-quotes. You only need to perform the registration once.

    11.1.0.1

    $OMS_HOME/bin/emctl register_connector connector -dd "<deployment_file>" -repos_pwd <password>
    

    10.2.0.5

    $OMS_HOME/bin/emctl register_connector connector -dd "<deployment_file>" -cs //<server>:<port>/<database_sid> -repos_user <username> -repos_pwd <password>
    

    10.2.0.4

    $OMS_HOME/bin/emctl register_connector connector “<deployment_file>” <server> <port> <database_sid> <username> <password> “<omshome>”
    

    Command Example

    $OMS_HOME/bin/emctl register_connector connector –dd 
    $OMS_HOME/sysman/connector/TEC_Connector/TECConnector.xml” 
    -repos_pwd password
    

The new TEC connector should now appear in the Management Connectors page after the emctl register_connector command has loaded the connector, as shown in Figure 2–2.

Figure 2-2 Installed TEC Connector

Lists installed TEC connector on conectors page

Table 2–2 provides descriptions for the parameters shown in the procedure above.

Table 2-2 emctl Parameters

Parameter Description

connector_name

Connector name. Specify "TEC Connector". The double quotes ( "" ) are mandatory.

connector_type_name

Connector type name. Specify "TEC Connector". The double quotes ( "" ) are mandatory.

database sid/ Service Name for RAC DB

Repository database instance ID or service name if you are using a RAC database as the repository.

deployment_file

Fully-qualified name of the connector deployment file. This TECConnector.xml file resides in the TEC connector directory $OMS_HOME/sysman/connector/TEC_Connector/.

description

Short description for the ticket template. This description is also displayed in Enterprise Manager.

internal_name

Internal name — Depending on the template, the values can be acknowledgeAlerts, createEvent, getNewAlerts, getUpdatedAlerts, or updateEvent.

jarfile

Fully-qualified name of the connector jar file. The jar file name is tec_connector.jar.

omshome

"<oraclehome>\oms10g" with double quotes recommended.

oraclehome

Top directory of the OMS installation.

password

Password for SYSMAN.

port

Listener port of the repository.

server

Host name of the Enterprise Manager repository.

template_name

Template name — Depending on the template, the values can be Acknowledge Alerts, Create Event, Get New Alerts, Get Updated Alerts, or Update Event.

template_type

Template type — Specify 1 for inbound transformation, 2 for outbound transformation, and 3 for xml.

template.xml

Fully-qualified name of the connector template file

username

Specify SYSMAN.


Registering Templates

To register templates for various Enterprise Manager versions:

  1. For each template, run the following emctl register_template connector command based on the appropriate Enterprise Manager version. The command must be run as a user with execute privilege on emctl and the ability to read the template.

    11.1.0.1

    $OMS_HOME/bin/emctl register_template connector -t <template.xml> -repos_pwd <password> -ctname <connector_type_name> -cname <connector_name> -tname <template_name> -iname  <internal_name> -ttype <template_type> -d <description>
    

    10.2.0.5

    $OMS_HOME/bin/emctl register_template connector -t <template.xml> -cs //<server>:<port>/<database sid> -repos_user <username> -repos_pwd <password> -ctname <connector_type_name> -cname <connector_name> -tname <template_name> -iname <internal_name> -ttype <template_type> -d <description>
    

    10.2.0.4

    No templates need to be registered for this version.

  2. Replace <template.xml>, <internal_name>, <template_name> and <template_type> with the values listed in Table 2-3, which lists the properties of each template for the IBM TEC Connector.

Table 2-3 Possible Replacement Values for register_template Parameters

template.xsl and template.xml internal_name template_name template_type

acknowledge_request.xsl

acknowledgeAlerts

Acknowledge Alerts

2

createEvent_request.xsl

createEvent

Create Event Request

2

createEvent_response.xsl

createEvent

Create Event Response

1

generic_request_acknowledgealerts.xml

acknowledgeAlerts

Acknowledge Alerts

3

getNewAlert_request.xsl

getNewAlerts

Get New Alerts Request

2

getNewAlerts_response.xsl

getNewAlerts

Get New Alerts Response

1

getUpdatedAlert_request.xsl

getUpdatedAlerts

Get Updated Alerts Request

2

getUpdatedAlerts_response.xsl

getUpdatedAlerts

Get Update Alerts Response

1

updateEvent_request.xsl

updateEvent

Update Event Request

2

updateEvent_response.xsl

updateEvent

Update Event Response

1

template_type Key:

template_type 1 — Inbound transformation

template_type 2 — Outbound transformation

template_type 3 — XML outbound transformation


The following version 11.1.0.1 examples are based on the template values shown in Table 2-3.

Example 2-1 Request XSL File for acknowledgeAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/acknowledge_request.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Acknowledge Alerts" -iname "acknowledgeAlerts" -ttype 2 -d "This is the request xsl file for acknowledgeAlerts method"

Example 2-2 Request XSL File for createEvent Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/createEvent_request.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Create Event Request" -iname "createEvent" -ttype 2 -d "This is the request xsl file for createEvent method"

Example 2-3 Response XSL File for createEvent Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/createEvent_response.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Create Event Response" -iname "createEvent" -ttype 1 -d "This is the response xsl file for createEvent method"

Example 2-4 Request XML File for acknowledgeAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/generic_request_acknowledgealerts.xml -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Acknowledge Alerts" -iname "acknowledgeAlerts" -ttype 3 -d "This is the request xml file for acknowledgeAlerts method"

Example 2-5 Request XSL File for getNewAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/getNewAlert_request.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Get New Alerts Request" -iname "getNewAlerts" -ttype 2 -d "This is the request xsl file for getNewAlerts method"

Example 2-6 Response XSL File for getNewAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/getNewAlerts_response.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Get New Alerts Response" -iname "getNewAlerts" -ttype 1 -d "This is the response xsl file for getNewAlerts method"

Example 2-7 Request XSL File for getUpdatedAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/getUpdatedAlert_request.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Get Updated Alerts Request" -iname "getUpdatedAlerts" -ttype 2 -d "This is the request xsl file for getUpdatedAlerts method"

Example 2-8 Response XSL File for getUpdatedAlerts Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/getUpdatedAlerts_response.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Get Updated Alerts Response" -iname "getUpdatedAlerts" -ttype 1 -d "This is the response xsl file for getUpdatedAlerts method"

Example 2-9 Request XSL File for updateEvent Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/updateEvent_request.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Update Event Request" -iname "updateEvent" -ttype 2 -d "This is the request xsl file for updateEvent method"

Example 2-10 Response XSL File for updateEvent Method

$OMS_HOME/bin/emctl register_template connector -t $OMS_HOME/sysman/connector/TEC_Connector/updateEvent_response.xsl -repos_pwd <password> -ctname "TEC Connector" -cname "TEC Connector" -tname "Update Event Response" -iname "updateEvent" -ttype 1 -d "This is the response xsl file for updateEvent method"