Adapter Installation Instructions for Oracle WebLogic Server
Topics
Note: Creating a foreign JNDI provider is required when the nms‑multispeak.ear is on a different managed server than the cesejb.ear; if they are deployed on the same server, skip this step.
Create a Managed Server (Optional)
To simplify creation of a new managed server, you may clone an existing Oracle Utilities Network Management System managed server.
Note: The URL for WebLogic will be http://hostname:port/console where hostname represents the DNS name or IP address of the Administration Server, and port represents the number of the port on which the Administration Server is listening for requests (port 7001 by default).
-DRMI_URL=t3://<hostname:port>
Create a Foreign JNDI Provider
In order for the Oracle Utilities Network Management System MultiSpeak Adapter, deployed on its own managed server, to communicate with the Oracle Utilities Network Management System (cesejb.ear), a foreign JNDI provider must be configured.
Note: Creating the foreign JNDI provider makes the cesejb.ear Enterprise JavaBeans (EJBs) appear local to the Oracle Utilities Network Management System MultiSpeak adapter.
Configure Foreign JNDI Provider
Initial Context Factory: weblogic.jndi.WLInitialContextFactory
Provider URL: JNDI provider URL for the NMS (cesejb.ear)
User: valid NMS user who belongs to the ‘nms-service’ group in WebLogic Server
Password: NMS user password
Confirm Password: enter the same NMS user password to confirm
Configure Data Source for the Adapters Managed Server
You may configure a new JDBC data source or add the adapter managed server as a target to an existing Oracle Utilities Network Management System read/write data source.
Note: See "Configure Database Connectivity" in the Oracle Utilities Network Management System Installation Guide for information on creating JDBC data sources.
Enabling Support for Plain HTTP
By default the adapter is configured to only accept incoming requests over HTTPS. To enable support for plain HTTP, add or uncomment the line in $NMS_CONFIG/jconfig/build.properties file:
option.no_multispeak_force_https
Then build new nms-multispeak.ear by running:
nms-install-config --java
Authentication Methods
By default the adapter is configured to use Basic HTTP Authentication for incoming web service requests. If credentials from the MultiSpeak message header should be used instead, add or uncomment the line in $NMS_CONFIG/jconfig/build.properties file:
option.no_multispeak_http_auth
Then build new nms-multispeak.ear by running:
nms-install-config --java
Note: This parameter has no effect on JMS transport mechanism available in the SCADA component of this adapter. It cannot use Basic HTTP Authentication mechanism.
The adapter authorizes incoming web service requests by checking that caller belongs to the group defined by the 'weblogic-ldap-group' parameter in the $NMS_CONFIG/jconfig/build.properties file.
Deploy the Adapter
Note: If you have not created additional Managed Servers or clusters, you will not see this assistant page.