This appendix describes the SCOM mappings and various other configuration defaults.
represents the format that the IBM TEC web service expects for creating new events in IBM TEC. The format for update requests is the same, except the root node would be "update" instead of "create."
Example A-1 Sample Format for IBM TEC Web Service
<iwaveaf:create xmlns:iwaveaf="http://iwavesoftware.com/services/ adapter-framework">
<event>
<description></description>
<status></status>
<severity></severity>
<repeatCount></repeatCount>
<createDate></createDate>
<eventClass>
<name>OracleEnterpriseManager</name>
</eventClass>
<group>
<name>PrimaryServer</name>
</group>
<object>
<computerName></computerName>
<displayName></displayName>
</object>
<source>
<computerName></computerName>
<name>OracleEnterpriseManager</name>
</source>
<extended-fields>
<string-field name="ext_id"></string-field>
<string-field name="sub_source">OracleEnterpriseManager</string-field>
</extended-fields>
</event>
</iwaveaf:create>
Table A-1 identifies the mappings between the IBM TEC base event slot names and the XML format that the IBM TEC web services uses. The XML document presented to the IBM TEC web service must have the corresponding fields set. This must be handled in the appropriate translation file identified in Table A-1.
Table A-1 Event Attributes and XML Path Mappings
| IBM TEC Slot Names | XML Path |
|---|---|
|
Class Name |
/create/event/eventClass/name |
|
msg |
/create/event/description |
|
status |
/create/event/status |
|
severity |
/create/event/severity |
|
repeat_count |
/create/event/repeatCount |
|
date |
/create/event/createDate |
|
fqhostname |
/create/event/object/computerName |
|
hostname |
/create/event/object/displayName |
|
source |
/create/event/source/name |
|
origin |
/create/event/source/computerName |
|
All other slot names |
See Extended Fields below. |
Extended fields pass information for slots that are not mapped. An extended field is defined as a <string-field/> element that is a child of the extended-fields node. The name of the slot is specified in the name attribute, and the value of the slot is specified in the element value.
In most cases, you can use the default port numbers that the IBM TEC web service uses. However, if there are any conflicts with existing applications, you need to change the port numbers.
8080 is the default port number for HTTP communication, and 8443 is the default port for HTTPS communication. To change the port number, perform the steps in the appropriate subsection.
The TEC web service uses port 8080 as the default port for communication when the web service is configured at installation to use HTTP (no SSL). To change the port number to a different value, perform the following steps at the system where the TEC web services are installed. Replace <TEC_INSTALL> with the directory where the TEC web services are installed.
Open a command prompt window and change the working directory to:
<TECWS_INSTALL>/adapters/conf
Make a back-up copy of the framework.properties file, then open the file with a text editor.
Replace all references to the old port number with the new port number, then save the file.
Restart the web service as instructed in Section 2.4.1.3, "Running the Web Service on Unix" and Section 2.4.2.4, "Running the Web Service on Windows".
Perform the following steps to change the URL the TEC connector is using:
From the Enterprise Manager console, click Setup.
Select Extensibility in the pane.
Select Management Connectors in the left pane.
Click the name of the TEC Connector.
The General tab of the Configure Management Connector page appears.
Change the URLs listed in the Web Service End Points section to use the new port number.
Click OK to save your changes.