Connecting to the CORBA interface

The probe connects to the target system through a CORBA interface.

To complete the connection, the probe needs a reference to the EmsSessionFactory_I object. The following topics contain:

A summary of the methods that the probe can use to obtain the reference to the EmsSessionFactory_I object.
Instructions on how to configure the probe for each of those methods.
Advice on how to use the messages in the log file to help confirm that you have configured the probe correctly or help you solve configuration problems.

Methods for obtaining a reference to the EmsSessionFactory_I object

The probe can obtain the object reference in one of two ways:

Using an IOR file
Using a Naming Service

Using an IOR file

When using Interoperable Object Reference (IOR) files, the probe obtains the reference to the EmsSessionFactory_I CORBA object from the IOR file specified in the IORFile property.

Using a Naming Service

As an alternative to an IOR file, the probe can use a Naming Service to obtain the reference to the EmsSessionFactory_I object. There are two ways that the probe can locate the Naming Service:

By using the host name and port number of the Naming Service specified in the NamingServiceHost and NamingServicePort properties.
By using the IOR file specified in the NamingServiceIORFile property.

The Naming Service then uses the value specified in the NamingContextPath property to obtain the reference to the EmsSessionFactory_I object.

Completing the connection sequence

Once the probe has obtained the reference to the EmsSessionFactory_I object, it logs in to the target system. It then creates an EMS session and queries the Subscriber and EMS Manager objects. The probe uses the Subscriber object to subscribe to real-time event notifications and the EMS Manager object to perform resynchronization operations.

Configuring the probe

Use the following procedure to configure the probe:

Decide on the method you want to use to obtain the reference to the EmsSessionFactory_I object.
Define values for the properties listed in the section for your chosen method.

IOR file

Set the IORFile property to the path for the Interoperable Object Reference (IOR) file used to connect to the target through CORBA. For example:

IORFile = "/opt/var/emssession.ior"

Locating the Naming Service using a specified host and port

Set the following properties:

NamingServiceHost: Set this property to the name of the host server that provides the Naming Service.
NamingServicePort: Set this property to the port on the host server to use to connect to the Naming Service.
NamingContextPath: Set this property to the full path of the EmsSessionFactory_I interface on the target system.
The following article in the Service Management Connect (SMC) technical community on IBM developerWorks shows how to construct the value of this property:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Netcool%20OMNIbus/page/How%20to%20configure%20naming%20context%20path%20for%20TMF%20standard%20Corba%20probe

For example:

NamingServiceHost = "nshost1"
NamingServicePort = "8054"
NamingContextPath = "TMF_MTNM.Class/TejasNetworks.Vendor/TejasNetworks\\
/NORTH-CDG.EmsInstance/3\\.5.Version/TejasNetworks\\/NORTH-CDG.EmsSessionFactory_I"

Locating the Naming Service using an IOR file

Set the following properties:

NamingServiceIORFile : Set this property to the path for the IOR file for the Naming Service.
NamingContextpath: Set this property to the path of the EmsSessionFactory interface.
The following article in the Service Management Connect (SMC) technical community on IBM developerWorks shows how to construct the value of this property:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#/wiki/Tivoli%20Netcool%20OMNIbus/page/How%20to%20configure%20naming%20context%20path%20for%20TMF%20standard%20Corba%20probe

For example:

NamingServiceIORFile = "/opt/var/ns.ior"
NamingContextPath = "TMF_MTNM.class/test/EmsSessionfactory_I"

Messages in the log file

Use the probe's log file to confirm that you configured the probe correctly or to help you solve configuration errors. The following sections contain the messages that appear for various connection situations.

Successful connection

This example shows the messages that occur in the log file on successfully connecting to the target system through a Naming Service running on a specified host and port:

Debug: D-JPR-000-000: Attempting to get reference for interface object       
Debug: D-JPR-000-000: Attempting to get object reference via ORBInitialHost and 
ORBInitialPort settings
Debug: D-JPR-000-000: Attempting to connect to Naming Service via host and 
port settings
Debug: D-JPR-000-000: Sucessfully connected
Debug: D-JPR-000-000: Attempting to resolve Naming Context to object reference
Debug: D-JPR-000-000: Narrowing reference to NamingContext
Debug: D-JPR-000-000: Successfully narrowed reference to Naming Context
Debug: D-JPR-000-000: Resolving Object  reference :
      TMF_MTNM.Class/TejasNetworks.Vendor/TejasNetworks\/NORTH-CDG.EmsInstance/3
\.5.Version/TejasNetworks\/NORTH-CDG.EmsSessionFactory_I
Debug: D-JPR-000-000: Resolved Object reference
Debug: D-JPR-000-000: Successfully found object reference
Debug: D-JPR-000-000: Narrowing object reference to interface object

No properties configured

The following example shows the messages that appear in the log file when none of the CORBA properties are configured:

Warning: W-JPR-000-000: NamingContextPath is empty, please ensure you have set 
this property if you want to connect to CORBA via Naming service
Error: E-JPR-000-000: IOR Object is null. Please check your probe settings.
Error: E-JPR-000-000: Failed to get IOR Object : IOR Object is null.
Error: E-JPR-000-000: Failed to connect: com.ibm.tivoli.netcool.omnibus.probe.
ProbeException: IOR Object is null.

IORFile property refers to an incorrect or invalid IOR file

The following example shows the messages that appear in the log file when the IORFile property refers to an incorrect or invalid IOR file:

Information: I-JPR-000-000: Read IOR file /home/netcool/sim/dist/var/ems.ior
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.
registerTarget ENTERING
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.bidi.CommandHandler.
registerTarget EXITING
Information: I-JPR-000-000: Converting string IOR to object reference : 
IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6
E746578744578743A312E300000000000010000000000000078000102000000000A3132372E302E31
2E310026250000001F5374616E646172644E532F4E616D655365727665722D504F412F5F726F6F740
0000000020000000000000008000000004A4143000000000100000024000000000501000100000002
000100010001000F00010109000000020501000100010100
Information: I-JPR-000-000: Retrieveing EMS Session via IOR object...
Error: E-JPR-000-000: Failed to get IOR Object : 
Error: E-JPR-000-000: Failed to connect: org.omg.CORBA.BAD_PARAM:   vmcid: 0x0  
minor code: 0  completed: No

Cannot connect when using the IORFile property

The following example shows the messages that can appear in the log file in these circumstances:

Invalid host, port, or host and port specified in he IOR file
Firewall issues
The target system is not online

Information: I-JPR-000-000: Read IOR file /home/netcool/sim/dist/var/
emssessionfactory.ior
Information: I-JPR-000-000: Converting string IOR to object reference : 
IOR:000000000000003F49444C3A6D746E6D2E746D666F72756D2E6F72672F656D7353657373696F
6E466163746F72792F456D7353657373696F6E466163746F72795F493A312E300000000000010000
000000000078000102000000000A3132372E302E312E310084B80000001F37383136373533383838
2F04221F100E034A1016100630463814141B484C1B00000000020000000000000008000000004A41
43000000000100000024000000000501000100000002000100010001000F00010109000000020501
000100010100
Information: I-JPR-000-000: Retrieveing EMS Session via IOR object...
Error: E-JPR-000-000: Failed to get interface version information: 
org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible  vmcid: IBM  
minor code: E07  completed: No
Error: E-JPR-000-000: Failed to connect: org.omg.CORBA.TRANSIENT: 
initial and forwarded IOR inaccessible  vmcid: IBM  minor code: E07  
completed: No

Not all properties set when connecting through a Naming Service host and port

The following example shows the messages that can appear in the log file when connecting through a Naming Service using a specified host and port. In this instance one of the NamingServiceHost, NamingServicePort and NamingContextPath properties has no value:

Warning: W-JPR-000-000: NamingContextPath is empty, please ensure you have 
set this property if you want to connect to CORBA via Naming service
Error: E-JPR-000-000: IOR Object is null. Please check your probe settings.
Error: E-JPR-000-000: Failed to get IOR Object : IOR Object is null.
Error: E-JPR-000-000: Failed to connect: com.ibm.tivoli.netcool.omnibus.probe.
ProbeException: IOR Object is null.
Debug: D-JPR-000-000: com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: IOR Object is null.

Properties have incorrect values when connecting through a Naming Service host and port

The following example shows the messages that can appear in the log file when connecting through a Naming Service using a specified host and port. In this instance, one or more of the NamingServiceHost, NamingServicePort and NamingContextPath properties has an incorrect value, or the host, port, or path is inaccessible:

Error: E-JPR-000-000: Failed to resolve initial references to the NamingService : 
NameService:org.omg.CORBA.COMM_FAILURE: purge_calls:2004 Reason: CONN_ABORT (1), 
State: ABORT (5)  vmcid: IBM  minor code: 306 completed: Maybe
Error: E-JPR-000-000: Failed to get IOR Object : 
org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: 
purge_calls:2004 Reason: CONN_ABORT (1), 
State: ABORT (5)  vmcid: IBM  minor code: 306 completed: Maybe
Error: E-JPR-000-000: Failed to connect: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.COMM_FAILURE: 
purge_calls:2004 Reason: CONN_ABORT (1), State: ABORT (5)  vmcid: IBM  
minor code: 306 completed: Maybe

Firewall configuration preventing connection to a Naming Server host or port

The following example shows the messages that can appear in the log file when configuration problems with a firewall prevent connection to the host or server of a Naming Service:

Debug: D-JPR-000-000: Resolving initial references to NamingService
Error: E-JPR-000-000: Failed to resolve initial references to the NamingService : 
NameService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: 
Unable to connect:host=127.0.0.1,port=9765  vmcid: IBM  minor code: E02  
completed: No
Error: E-JPR-000-000: Failed to get IOR Object : 
org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: 
java.net.ConnectException: Unable to connect:host=127.0.0.1,port=9765  vmcid: IBM  
minor code: E02  completed: No
Error: E-JPR-000-000: Failed to connect: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CORBA.ORBPackage.InvalidName: NameService:org.omg.CORBA.TRANSIENT: 
java.net.ConnectException: Unable to connect:host=127.0.0.1,port=9765  vmcid: IBM  
minor code: E02  completed: No

Incorrect NamingContextPath or the Naming Server is offline

The following example shows the messages that can appear in the log file in these circumstances:

An incorrect value for the NamingContextPath property means the ORB is unable to narrow the configured context path on the target system.
The host server for the Naming Service is offline.

Error: E-JPR-000-000: Failed to get the System reference from the naming 
service! : 
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Error: E-JPR-000-000: Failed to resolved to Naming Context :
org.omg.CosNaming.NamingContextPackage.NotFound: 
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Error: E-JPR-000-000: Failed to get IOR Object : 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CosNaming.NamingContextPackage.NotFound: 
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
Error: E-JPR-000-000: Failed to connect: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CosNaming.NamingContextPackage.NotFound: 
IDL:omg.org/CosNaming/NamingContext/NotFound:1.0

IORFile or NamingServiceIORFile specifies an incorrect path

The following example shows the messages that can appear in the log file when the path specified by the IORFile or NamingServiceIORFile is incorrect and the probe cannot find the IOR file:

Error: E-JPR-000-000: Failed to get object from Naming Service IOR  file: 
Failed to find file /home/netcool/sim/dist/var/em.ior: 
java.io.FileNotFoundException: /home/netcool/sim/dist/var/em.ior

NamingServiceIORFile specifies an incorrect IOR file or the IOR is incorrect

The following example shows the messages that appear in the log file when the value of the NamingServiceIORFile property refers to an incorrect IOR file or to a file that specifies and incorrect IOR:

Error: E-JPR-000-000: Failed to connect to the NamingService : 
Error: E-JPR-000-000: Failed to resolve to the naming context: 
org.omg.CORBA.BAD_PARAM:   vmcid: 0x0  minor code: 0  completed: No
Error: E-JPR-000-000: Failed to get IOR Object : 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CORBA.BAD_PARAM:   vmcid: 0x0  minor code: 0  completed: No
Error: E-JPR-000-000: Failed to connect: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
com.ibm.tivoli.netcool.omnibus.probe.ProbeException: 
org.omg.CORBA.BAD_PARAM: