Index
A B C D E G H I J K L M N O P Q R S T U W X
A
- acknowledge_request.xml, 3.3.2
- Add Target Page, data exchange connectors, 4.3.2
- adding or deleting nodes, 1.1
- agent properties, querying, 1.8, 1.8
- Agent, assigning privileges, 1.3.3
- aggregate target types, 1.7.1
- aggregate target, querying for members of, 1.7.3
- architecture of data exchange connectors, 4.1
- auto ticketing, help desk connectors, 2.1
B
- building Oracle Clusterware and Database images, 1.3.4
C
- cleanup_request.xml, 3.3.2
- configuration, testing for help desk, 2.6
- connector descriptor XML file, sample of, 3.3.1
- Connector Framework
-
- event connectors, 3.1
- installing, 1.4
- limitations of, 1.2
- overview of, 1.1
- prerequisites, 1.3
- setting up emcli, 1.3.2
- system requirements, 1.3.1
- uninstalling, 1.5
- connectors
-
- adding or deleting nodes, 1.1
- available tasks, 1.1
- creating Real Application Clusters (RAC) database, 1.1
- getModel interface, 1.7
- limitations of Connector Framework, 1.2
- prerequisites of Connector Framework, 1.3
- querying Enterprise Manager data, 1.1
- setModel interface, 1.7
- setting up emcli, 1.3.2
- system requirements of Connector Framework, 1.3.1
- Web services interfaces, 1.1
- connectorType.xsd file, 3.3.1
- connectorType.XSD file, help desk connectors, 2.3.2
- Create Ticket Web service, 2.2
- createEvent, event connectors and, 3.7.1
- createEvent_request.xsl transformation file example, 3.7.2
- createEvent_response.xsl response transformation file example, 3.7.3
- creating
-
- base of RAC image, 1.3.4
- one-node RAC, 1.9.2, 1.9.2
- Real Application Clusters (RAC) database, 1.1
D
- data exchange
-
- OBAM artifacts for inbound session, 4.4.3
- data exchange connectors, 4.4.2.1, 4.4.2.1
-
- Add Target Page, 4.3.2
- architecture, 4.1
- checking logs, 4.6.4
- creating a data exchange hub, 4.3.1
- data exchange hub, 4.2.1
- data flow tips, 4.6.3
- denormalized message format, 4.2.3.2
- EM-BAM data objects, 4.4.2.1
- EM-BAM EMS definitions, 4.4.2.1
- hub setup, 4.4.2.3
- importing OBAM artifacts, 4.4.2.1
- inbound alert schema, 4.3.7.3
- inbound indicators schema, 4.3.7.1
- inbound JMS topics, 4.3.6
- inbound message schemas, 4.3.7
- JMS topic names, 4.3.3
- JNDI details, 4.6.3
- message example defaults, 4.3.7.2
- normalized message format, 4.2.3.1
- notification method, 4.6.2
- notification rules, 4.6.2
- OBAM Architect Screen, 4.4.2.2
- OBAM server tips, 4.6.5
- qualified XML message sample, 4.3.7.1
- Select Business Events/Indicators Page, 4.3.5
- Session Setup Page, 4.3.2, 4.3.5
- setting up, 4.3
- setting up data flow, 4.4.2
- unqualified XML message sample, 4.3.7.1
- updating JNDI, 4.4.2.2
- data fields, Enterprise Manager, 2.3.3
- database target properties, querying, 1.8, 1.8
- defining metrics example, event connectors, 3.8
- delete node response model, job ID in, 1.9.4
- denormalized message format, outbound message schema, 4.3.4.2
- deployment descriptor file example, event connectors, 3.7.1
E
- EM-BAM
-
- data objects, 4.4.2.1, 4.4.2.1
- EMS definitions, 4.4.2.1
- enterprise link plans, 4.4.2.1
- EM-BAM data objects, 4.4.2.1
- EM-BAM enterprise link plans, 4.4.2.1
- emcli, setting up, 1.3.2
- emctl parameters
-
- event connectors, 3.4
- help desk connectors, 2.4
- EMEventResponse.xsd schema, event connectors, 3.7.3
- EMEvent.xsd schema, event connectors, 3.7.2
- EMModel.xsd schema, 1.7.4
- Enterprise Manager
-
- data fields, help desk connectors, 2.3.3
- repository properties, querying, 1.8, 1.8
- error case, handling for request model, 1.10
- event connectors
-
- acknowledge_request.xml, 3.3.2
- adding more instance properties, 3.6.2
- cleanup_request.xml, 3.3.2
- configuring, 3.5
- connector descriptor XML file, 3.3.1, 3.3.1
- connectorType.xsd file, 3.3.1
- createEvent, 3.7.1
- createEvent_request.xsl transformation file example, 3.7.2
- createEvent_response.xsl response transformation file example, 3.7.3
- creating additional target instances, 3.6.1
- default request XML files, description of, 3.3.2
- default request XSL files, description of, 3.3.3
- defining key fields, 3.8
- defining metrics example, 3.8
- deploying, 3.4
- deployment descriptor file example, 3.7.1
- emctl parameters, 3.4
- EMEventResponse.xsd schema, 3.7.3
- EMEvent.xsd schema, 3.7.2
- enabling SSL for HTTPS, 3.9
- generic_request_newalerts.xml, 3.3.2
- generic_request_updatedalerts.xml, 3.3.2
- getNewAlerts_response.xsl, 3.3.4
- getUpdatedAlerts_response.xsl, 3.3.4
- initialize_request.xml, 3.3.2
- metadata files required, 3.1
- metadata for getResponse operation, 3.3.7
- packaging, 3.4
- prerequisites, 3.1, 3.2
- response XSL files, description of, 3.3.4
- setup_request.xml, 3.3.2
- setup_response.xsl, 3.3.4
- targetType.xml file example, 3.3.5
- uninitialize_request.xml, 3.3.2
- updateEvent, 3.7.1
- updateEvent_request.xsl transformation file example, 3.7.2
- updateEvent_response.xsl response transformation file example, 3.7.3
- Wallet Manager, 3.9.3
- example response transform for Remedy, 2.3.4
G
- generic_request_newalerts.xml, 3.3.2
- generic_request_updatedalerts.xml, 3.3.2
- Get Ticket Web service, 2.2
- getModel connector interface, 1.7
- getNewAlerts_response.xsl, 3.3.4
- getTicket and response XSL file, 2.3.4
- getTicket_request.xsd XML schema, 2.6.1
- getTicket_response.xsd XML schema, 2.6.2
- getUpdatedAlerts_response.xsl, 3.3.4
H
- help desk connectors
-
- auto ticketing, 2.1
- configuring, 2.5
- connectorType.XSD file, 2.3.2
- deploying, 2.4
- emctl parameters, 2.4
- enabling SSL for HTTPS, 2.7
- Enterprise Manager data fields, 2.3.3
- getTicket_request.xsd XML schema, 2.6.1
- getTicket_response.xsd XML schema, 2.6.2
- manual ticketing, 2.1
- metadata files, 2.1
- Notification Rules, 2.1
- packaging, 2.4
- prerequisites, 2.2
- sample descriptor XML file, 2.3.1
- testing the configuration, 2.6
- ticket template schema, 2.3.3
- Wallet Manager, 2.7.3
- host properties, querying, 1.8, 1.8
- hub setup, data exchange connectors, 4.4.2.3
I
- importing OBAM artifacts, 4.4.2.1
- inbound alert schema, 4.3.7.3
- inbound indicators schema, 4.3.7.1
- initialize_request.xml, 3.3.2
J
- JMS topic names, data exchange connectors, 4.3.3
- JNDI details, data exchange connectors, 4.6.3
- job ID
-
- in CreateRAC response model, 1.9.2
- in delete node response model, 1.9.4
- in extentRAC response model, 1.9.3
- job status, querying, 1.8
K
- key fields, defining for event connectors, 3.8
L
- limitations of Connector Framework, 1.2
- list of targets, querying for, 1.7.3
- listener properties, querying, 1.8, 1.8
M
- manual ticketing, help desk connectors, 2.1
- message example defaults, 4.3.7.2
- metadata files
-
- help desk connectors, 2.1
- required for event connectors, 3.1
- metadata for getResponse operation, 3.3.7
- model target types, 1.7.1
N
- node
-
- deleting from existing RAC, 1.9.4
- job ID in delete node response model, 1.9.4
- normalized alert message, outbound message schema, 4.3.4.1
- normalized message format, outbound message schema, 4.3.4.1
- normalized metric data message, outbound message schema, 4.3.4.1
- normalized metric message, outbound message schema, 4.3.4.1
- normalized security filter message, outbound message schema, 4.3.4.1
- normalized target message, outbound message schema, 4.3.4.1
- notification method, data exchange connectors, 4.6.2
- notification rules
-
- data exchange connectors, 4.6.2
- help desk connectors, 2.1
O
- OBAM
-
- Architect Screen, 4.4.2.2
- artifacts for inbound session, 4.4.3
- EM-BAM data objects, 4.4.2.1, 4.4.2.1
- EM-BAM EMS definitions, 4.4.2.1
- EM-BAM enterprise links plans, 4.4.2.1
- importing artifacts, 4.4.2.1
- server tips, 4.6.5
- setting up data flow, 4.4.2
- updating JNDI, 4.4.2.2
- Oracle Clusterware properties, querying, 1.8, 1.8
- Oracle Clusterware, building, 1.3.4
- Oracle Database images, building, 1.3.4
- Oracle Universal Installer (OUI)
-
- installing Agent from, 1.3.4
- starting, 1.4
- outbound message schema
-
- denormalized message format, 4.3.4.2
- normalized alert message, 4.3.4.1
- normalized message format, 4.3.4.1
- normalized metric data message, 4.3.4.1
- normalized metric message, 4.3.4.1
- normalized security filter message, 4.3.4.1
- normalized target message, 4.3.4.1
P
- prerequisites
-
- Connector Framework, 1.3
- event connectors, 3.1, 3.2
- help desk connectors, 2.2
- Windows OMS, 1.9.1
- privileges
-
- assigning for Windows Agent, 1.3.3
- assigning for Windows NT, 1.3.3.1
- assigning for Windows Server, 1.3.3.1
- assigning for Windows XP, 1.3.3.2
- property elements
-
- querying, 1.7.2
- setting, 1.7.2
Q
- qualified XML message sample, 4.3.7.1
- querying
-
- agent properties, 1.8, 1.8
- database target properties, 1.8, 1.8
- Enterprise Manager data, 1.1
- Enterprise Manager repository properties, 1.8, 1.8
- host properties, 1.8, 1.8
- job status, 1.8
- list of targets, 1.7.3
- listener properties, 1.8, 1.8
- member of an aggregate target, 1.7.3
- Oracle Clusterware properties, 1.8, 1.8
- property elements, 1.7.2
- RAC properties, 1.8, 1.8
R
- RAC
-
- adding note to an existing RAC, 1.9.3
- creating base of RAC image, 1.3.4
- creating one-node RAC, 1.9.2, 1.9.2
- deleting node from existing RAC, 1.9.4
- job ID in CreateRAC response model, 1.9.2
- job ID in delete node response model, 1.9.4
- job ID in extentRAC response model, 1.9.3
- properties, querying, 1.8, 1.8
- provisioning operation, preparing and activating images, 1.3.4
- Remedy Connector sample ticket template, 2.3.3
- request and response model schema, 1.7.4
- request model, handling error for, 1.10
- response XSL file
-
- example response transform for Remedy, 2.3.4
- getTicket, 2.3.4
S
- sample connector descriptor XML file, 2.3.1, 3.3.1
- sample ticket template, Remedy Connector, 2.3.3
- schema
-
- EMModel.xsd, 1.7.4
- getTicket_request.xsd XML, 2.6.1
- getTicket_response.xsd XML, 2.6.2
- ticket templates, 2.3.3
- Select Business Events/Indicators Page, data exchange connectors, 4.3.5
- Session Setup Page, data exchange connector, 4.3.2, 4.3.5
- setModel API, 1.9
- setModel connector interface, 1.7
- setting property elements, 1.7.2
- setup_request.xml, 3.3.2
- setup_response.xsl, 3.3.4
- SSL for HTTPS
-
- event connectors, 3.9
- help desk connectors, 2.7
- system requirements of Connector Framework, 1.3.1
T
- target instances, creating for event connectors, 3.6.1
- target types
-
- aggregate, 1.7.1
- model, 1.7.1
- targetType.xml file example, 3.3.5
- targetType.xml, adding more instance properties, 3.6.2
- tasks available for connectors, 1.1
- ticket templates
-
- default XSL files, 2.3.3
- sample Remedy Connector template, 2.3.3
U
- uninitialize_request.xml, 3.3.2
- unqualified XML message sample, 4.3.7.1
- Update Ticket Web service, 2.2
- updateEvent, event connectors and, 3.7.1
- updateEvent_request.xsl transformation file example, 3.7.2
- updateEvent_response.xsl response transformation file example, 3.7.3
- updating JNDI, 4.4.2.2
W
- Wallet Manager
-
- event connectors, 3.9.3
- help desk connectors, 2.7.3
- Web service client stub, generating, 1.6
- Web services
-
- Create Ticket, 2.2
- Get Ticket, 2.2
- Update Ticket, 2.2
- Web services interfaces, Connector Framework and, 1.1
- Windows NT, setting privileges, 1.3.3.1
- Windows OMS, prerequisites, 1.9.1
- Windows Server 2003
-
- changing log on property, 1.9.1
- setting privileges, 1.3.3
- Windows Server, setting priviliges, 1.3.3.1
- Windows XP, setting privileges, 1.3.3.2
X
- XSL files, default ticket template, 2.3.3