Adapter Installation Instructions for Oracle WebLogic Server
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.
1.
|
Log in to the WebLogic Server Administration Console.
|
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).
3.
|
In the Domain Structure tree, expand Environment, then select Servers to open the Summary of Servers page.
|
4.
|
Select an Oracle Utilities Network Management System server in the Servers table and click Clone.
|
5.
|
Click the link to the cloned server and edit the settings:
|
a.
|
On the General tab, change the Listen Port and SSL Listen Port to unique values.
|
b.
|
On the Server Start tab, edit the Arguments field to remove the DRMI_URL parameter:
|
-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.
1.
|
Log in to the WebLogic Server Administration Console.
|
3.
|
In the Domain Structure tree, expand Services, then select Foreign JNDI Providers to open the Summary of Foreign JNDI Providers page.
|
4.
|
On the Summary of Foreign JNDI Providers page, click New.
|
5.
|
Enter a name for the new Foreign JNDI Provider.
|
Configure Foreign JNDI Provider
1.
|
In the Foreign JNDI Provider table, click the new foreign JNDI provider name link.
|
2.
|
In the Settings for Foreign_JNDI_Provider_Name
General tab, enter the following information:
|
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
5.
|
Create the following foreign JNDI links
|
7.
|
Select the managed server where the Oracle Utilities Network Management System MultiSpeak adapter will be deployed and click Save.
|
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.
1.
|
In the Domain Structure tree, expand Services, then select Data Sources.
|
2.
|
In the Data Sources table, click the data source name (either a new data source or an existing read/write NMS data source) to open the Settings for JDBC_Data_Source_Name page.
|
4.
|
Add the adapter managed server to the list of targets.
|
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
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.
1.
|
In the left pane of the Administration Console, select Deployments.
|
2.
|
In the right pane, click Install.
|
3.
|
In the Install Application Assistant, locate the nms-multispeak.ear file.
|
5.
|
Select Install this deployment as an application.
|
7.
|
Select the servers and/or clusters to which you want to deploy the application.
|
Note: If you have not created additional Managed Servers or clusters, you will not see this assistant page.
9.
|
Set the deployed name of the application to: nms-multispeak.
|
11.
|
Review the configuration settings you have specified.
|
12.
|
Click Finish to complete the installation.
|