A Connector Tips

Recommended Protocol

Oracle recommends that you use HTTPS as the protocol for the communication between Enterprise Manager and the CASD Adapter. Use HTTP only if a secure connection is not required and the data can be transferred in clear text between the two systems.

Supported Alerts

This release supports the following types of alerts:

• Metric alerts

• Availability alerts

Changing the Default Adapter Port

In most cases, you can use the default port numbers that the CASD Adapter uses. However, if there are any conflicts with existing applications, you need to change the port numbers.

8082 is the default port number for HTTP communication, and 8443 is the default port for HTTPS communication. To change the port number, perform the following steps on the system where the CASD Adapter is installed. Replace the <dir> in this example with the directory where the adapter is installed.

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

   <dir>/adapters/conf
   

2. Make a backup copy of the framework.properties file.

3. Enter the following commands to configure the adapter to use a different port, where <prot> is the protocol (HTTP or HTTPS) and <newPort> is the new port number:

   ..\bin\propertiesEditor.bat -p services.url=<prot>://localhost:<newPort>/services framework.properties

   ..\bin\propertiesEditor.bat -p notification.url=<prot>://localhost:<newPort>/services/notification framework.properties

   ..\bin\propertiesEditor.bat -p acquisitionevent.url=<prot>://localhost:<newPort>/services/acquisition-event framework.properties

   The propertiesEditor.bat script is intended specifically for the Windows platform. The equivalent script for Unix platforms is propertiesEditor.sh.

4. If the protocol being used is HTTPS, additional changes are required. Perform the following steps to complete the additional requirements.

   • Copy the framework.xml file from the <dir>/adapters/endpoints/ca-usd directory to the <dir>/adapters/conf directory.

   • Open the framework.xml file in the adapters/conf directory with a text editor.

   • Change port 8443 to the new port number and save the file.

5. Change the working directory to ../bin.

6. Enter the following command to restart the CASD Adapter.

   • If the web service is installed on a Unix system:

     ./service.sh restart

   • If the web service is installed on a Windows system as a standalone application, close the window where the adapter was running, then run:

     startAdapters.bat

   • If the web service is installed on a Windows system as a Windows service, enter the following commands:

     net stop iWaveAdapters

     net start iWaveAdapters

Perform the following steps to change the URL the CA Service Desk connector is using:

1. Log in to the Oracle Enterprise Manager console with an account that has Super Administrator privileges.

2. From the Setup menu of the Enterprise Manager console, select Extensibility, then Management Connectors.

   The Management Connectors page appears.

3. Click on the name of the CA Service Desk connector.

   This invokes edit mode, enabling you to configure the connector.

4. Change the URLs listed in the Web Service End Points section to use the new port number.

5. Click OK.

Using the Correct URL for CASD Adapter Operations

Perform the following steps to identify and configure the connector to use the correct URL for CASD Adapter operations.

1. Open a command terminal on the system where the CASD Adapter is installed.

2. Change the working directory to the adapters/log directory in the CASD Adapter installation directory.

3. Open the framework.log file in a text editor.

4. Go to the bottom of the file and search backwards for the string iWave Adapter Framework Started. This indicates that the adapter was successfully started.

   Note:

   If the string is not in the file, the log file might have exceeded the maximum size and rolled over. Restart the adapter and wait for it to complete the startup process. The adapter adds a line that contains iWave Adapter Framework Started when it has successfully started.

5. Go to the bottom of the framework.log file and search backwards for the string "Setting the server's publish address to be." Continue searching backwards until the URL that contains /IncidentService is found. This is the URL that should be specified when configuring the connector for the createTicket, getTicket, and updateTicket operations.