JMS connections

Overview

A JMS client requires the following to establish an NFM-P JMS connection:

initial JMS context configuration
each NFM-P main server IP address or hostname
the appropriate samOss.jar file
NFM-P user credentials

The user account requires an assigned scope of command profile that includes the OSS management role. The user password can be MD5-hashed or plain text.

Note: MD5-hashed passwords do not secure the communication channel.

If a firewall is between a main server and an OSS client, you must ensure that the firewall allows traffic to and from the required ports. See the NSP Planning Guide for the list of ports required for the NFM-P JMS.

Initial context configuration

Note: The JNP JNDI context is deprecated and will be removed in the future. The JNDI context for looking up the JMS connection factory is now based on remoting. Nokia recommends that you update each JMS OSS application to use remoting-based JNDI context attributes.

See the /opt/nsp/nfmp/server/nms/integration/SAM_O/jmsexample/README file on an NFM-P main server for more information.

The NFM-P JMS requires a user name and password for the JNDI initial context lookup. You can set the JNDI parameters in the client environment, or in a JNDI properties file on the client station; an environment value overrides a file value.

Nokia recommends that you set the JNDI parameters in the JNDI properties file, as described in To configure the initial JMS context , rather than in the environment, to facilitate the maintenance of JNDI parameter changes. The JNDI automatically reads the file if the file is in the client Java class path.

samOss.jar

WARNING

Equipment Damage

An OSS client must use the samOss.jar from the current NFM-P release.

If a different samOss.jar is used, the NFM-P system may become unstable. The NFM-P release information is in the JAR manifest file.

The samOss.jar file contains the classes required to connect to the XML API. If an OSS client must connect to multiple NFM-P systems at different releases, the OSS must use separate JVMs and the appropriate samOss.jar file for each NFM-P release. Alternatively, an OSS client can use multiple class loader instances in one JVM to access multiple samOss.jar versions.

Obtaining the samOss.jar file

To compile and connect an NFM-P JMS client describes how to obtain the samOss.jar file, and how to configure and test a JMS connection.

Use subject to agreed restrictions on disclosure and use.