Index
A C D E G H I J K M N O P Q R S T U W X
A
- acknowledge_request.xml, 2.3.4
- Add Target Page, data exchange connectors, 3.3.2
- architecture of data exchange connectors, 3.1
- auto ticketing, help desk connectors, 1.1
C
- cleanup_request.xml, 2.3.4
- configuration, testing for help desk, 1.6
- connector descriptor XML file, sample of, 2.3.1
- Connector Framework
-
- event connectors, 2.1
- connectorType.xsd file, 2.3.1
- connectorType.XSD file, help desk connectors, 1.3.2
- Create Ticket Web service, 1.2
- createEvent, event connectors and, 2.7.1
- createEvent_request.xsl transformation file example, 2.7.2
- createEvent_response.xsl response transformation file example, 2.7.3
D
- data exchange
-
- OBAM artifacts for inbound session, 3.4.3
- data exchange connectors, 3.4.2.2, 3.4.2.2, 3.4.2.2
-
- Add Target Page, 3.3.2
- architecture, 3.1
- checking logs, 3.6.4
- creating a data exchange hub, 3.3.1
- data exchange hub, 3.2.1
- data flow tips, 3.6.3
- denormalized message format, 3.2.3.2
- EM-BAM data objects, 3.4.2.1
- EM-BAM EMS definitions, 3.4.2.1
- importing OBAM artifacts, 3.4.2.1
- inbound alert schema, 3.3.7.3
- inbound indicators schema, 3.3.7.1
- inbound JMS topics, 3.3.6
- inbound message schemas, 3.3.7
- JNDI details, 3.6.3
- message example defaults, 3.3.7.2
- normalized message format, 3.2.3.1
- notification method, 3.6.2
- notification rules, 3.6.2
- OBAM Architect Screen, 3.4.2.2
- qualified XML message sample, 3.3.7.1
- Select Business Events/Indicators Page, 3.3.5
- Session Setup Page, 3.3.2, 3.3.5
- setting up, 3.3
- setting up data flow, 3.4.2
- unqualified XML message sample, 3.3.7.1
- updating JNDI, 3.4.2.2
- data fields, Enterprise Manager, 1.3.3
- defining metrics example, event connectors, 2.3.2.2
- denormalized message format, outbound message schema, 3.3.4.2
- deployment descriptor file example, event connectors, 2.7.1
E
- EM-BAM
-
- data objects, 3.4.2.1, 3.4.2.2, 3.4.2.2
- EMS definitions, 3.4.2.1
- enterprise link plans, 3.4.2.2
- EM-BAM data objects, 3.4.2.2, 3.4.2.2
- EM-BAM enterprise link plans, 3.4.2.2
- emctl parameters
-
- help desk connectors, 1.4, 2.4
- EMEventResponse.xsd schema, event connectors, 2.7.3
- EMEvent.xsd schema, event connectors, 2.7.2, 2.7.2
- Enterprise Manager
-
- data fields, help desk connectors, 1.3.3
- event connectors
-
- acknowledge_request.xml, 2.3.4
- adding more instance properties, 2.3.2.1
- cleanup_request.xml, 2.3.4
- configuring, 2.5
- connector descriptor XML file, 2.3.1, 2.3.1
- connectorType.xsd file, 2.3.1
- createEvent, 2.7.1
- createEvent_request.xsl transformation file example, 2.7.2
- createEvent_response.xsl response transformation file example, 2.7.3
- creating additional target instances, 2.6.1
- default request XSL files, description of, 2.3.5
- defining key fields, 2.3.2.2
- defining metrics example, 2.3.2.2
- deploying, 2.4
- deployment descriptor file example, 2.7.1
- EMEventResponse.xsd schema, 2.7.3
- EMEvent.xsd schema, 2.7.2, 2.7.2
- enabling SSL for HTTPS, 2.8
- generic_request_newalerts.xml, 2.3.4
- generic_request_updatedalerts.xml, 2.3.4
- getNewAlerts_response.xsl, 2.3.6
- getUpdatedAlerts_response.xsl, 2.3.6
- initialize_request.xml, 2.3.4
- metadata files required, 2.1
- metadata for getResponse operation, 2.3.7
- packaging, 2.4
- prerequisites, 2.1, 2.2
- response XSL files, description of, 2.3.6
- setup_request.xml, 2.3.4
- setup_response.xsl, 2.3.6
- targetType.xml file example, 2.3.2
- uninitialize_request.xml, 2.3.4
- updateEvent, 2.7.1
- updateEvent_request.xsl transformation file example, 2.7.2
- updateEvent_response.xsl response transformation file example, 2.7.3
- example response transform for Remedy, 1.3.4
G
- generic_request_newalerts.xml, 2.3.4
- generic_request_updatedalerts.xml, 2.3.4
- Get Ticket Web service, 1.2
- getNewAlerts_response.xsl, 2.3.6
- getTicket and response XSL file, 1.3.4
- getTicket_request.xsd XML schema, 1.6.1
- getTicket_response.xsd XML schema, 1.6.2
- getUpdatedAlerts_response.xsl, 2.3.6
H
- help desk connectors
-
- auto ticketing, 1.1
- configuring, 1.5
- connectorType.XSD file, 1.3.2
- deploying, 1.4
- emctl parameters, 1.4, 2.4
- enabling SSL for HTTPS, 1.7
- Enterprise Manager data fields, 1.3.3
- getTicket_request.xsd XML schema, 1.6.1
- getTicket_response.xsd XML schema, 1.6.2
- manual ticketing, 1.1
- metadata files, 1.1
- Notification Rules, 1.1
- packaging, 1.4
- prerequisites, 1.2
- sample descriptor XML file, 1.3.1
- testing the configuration, 1.6
- ticket template schema, 1.3.3
- Wallet Manager, 1.7.3, 2.8.3
I
- importing OBAM artifacts, 3.4.2.1
- inbound alert schema, 3.3.7.3
- inbound indicators schema, 3.3.7.1
- initialize_request.xml, 2.3.4
J
- JNDI details, data exchange connectors, 3.6.3
K
- key fields, defining for event connectors, 2.3.2.2
M
- manual ticketing, help desk connectors, 1.1
- message example defaults, 3.3.7.2
- metadata files
-
- help desk connectors, 1.1
- required for event connectors, 2.1
- metadata for getResponse operation, 2.3.7
N
- normalized alert message, outbound message schema, 3.3.4.1
- normalized message format, outbound message schema, 3.3.4.1
- normalized metric data message, outbound message schema, 3.3.4.1
- normalized metric message, outbound message schema, 3.3.4.1
- normalized security filter message, outbound message schema, 3.3.4.1
- normalized target message, outbound message schema, 3.3.4.1
- notification method, data exchange connectors, 3.6.2
- notification rules
-
- data exchange connectors, 3.6.2
- help desk connectors, 1.1
O
- OBAM
-
- Architect Screen, 3.4.2.2
- artifacts for inbound session, 3.4.3
- EM-BAM data objects, 3.4.2.1, 3.4.2.2, 3.4.2.2
- EM-BAM EMS definitions, 3.4.2.1
- EM-BAM enterprise links plans, 3.4.2.2
- importing artifacts, 3.4.2.1
- setting up data flow, 3.4.2
- updating JNDI, 3.4.2.2
- outbound message schema
-
- denormalized message format, 3.3.4.2
- normalized alert message, 3.3.4.1
- normalized message format, 3.3.4.1
- normalized metric data message, 3.3.4.1
- normalized metric message, 3.3.4.1
- normalized security filter message, 3.3.4.1
- normalized target message, 3.3.4.1
P
- prerequisites
-
- event connectors, 2.1, 2.2
- help desk connectors, 1.2
Q
- qualified XML message sample, 3.3.7.1
R
- Remedy Connector sample ticket template, 1.3.3
- response XSL file
-
- example response transform for Remedy, 1.3.4
- getTicket, 1.3.4
S
- sample connector descriptor XML file, 1.3.1, 2.3.1
- sample ticket template, Remedy Connector, 1.3.3
- schema
-
- getTicket_request.xsd XML, 1.6.1
- getTicket_response.xsd XML, 1.6.2
- ticket templates, 1.3.3
- Select Business Events/Indicators Page, data exchange connectors, 3.3.5
- Session Setup Page, data exchange connector, 3.3.2, 3.3.5
- setup_request.xml, 2.3.4
- setup_response.xsl, 2.3.6
- SSL for HTTPS
-
- event connectors, 2.8
- help desk connectors, 1.7
T
- target instances, creating for event connectors, 2.6.1
- targetType.xml file example, 2.3.2
- targetType.xml, adding more instance properties, 2.3.2.1
- ticket templates
-
- default XSL files, 1.3.3
- sample Remedy Connector template, 1.3.3
U
- uninitialize_request.xml, 2.3.4
- unqualified XML message sample, 3.3.7.1
- Update Ticket Web service, 1.2
- updateEvent, event connectors and, 2.7.1
- updateEvent_request.xsl transformation file example, 2.7.2
- updateEvent_response.xsl response transformation file example, 2.7.3
- updating JNDI, 3.4.2.2
W
- Wallet Manager
-
- help desk connectors, 1.7.3, 2.8.3
- Web services
-
- Create Ticket, 1.2
- Get Ticket, 1.2
- Update Ticket, 1.2
X
- XSL files, default ticket template, 1.3.3