WebLogic Configuration
The FLEX SCADA module requires 3 new JMS queues and a JMS Connection Factory.
The JMS message queues are:
• scada-analog-queue with a JDNI name jms/scada-analog-queue
• scada-digital-queue with a JDNI name jms/scada-digital-queue
• scada-status-queue with a JDNI name jms/scada-status-queue
The JMS connection factory is:
• ScadaConnectionFactory with a JNDI name jms/ScadaConnectionFactory
Creating a JMS Message Queue
To create a new JMS Message Queue:
1. Open the WebLogic Server Administration Console.
2. Select Messaging and then select JMS Modules.
3. Select the JMS Module (for example, SystemModule-1).
4. Click New.
5. Select Queue and then Next.
6. Enter the name of the JMS Queue (for example, scada-analog-queue).
7. Enter the JNDI name of the queue (for example, jms/scada-analog-queue).
8. Click Next
9. Select Create a New Subdeployment. Confirm the sub deployment name matches the queue name.
10. Click OK
11. Select the target deployment (for example, JMSServer-1).
12. Click Finish
Creating a JMS Connection Factory
To create a new JMS Connection Factory:
1. Open the Weblogic Server Administration Console.
2. Select Messaging and then select JMS Modules.
3. Select the JMS Module, (for example, SystemModule-1).
4. Click New.
5. Select Connection Factory and then Next.
6. Enter the name of the Connection Factory (for example, ScadaConnectionFactory).
7. Enter the JNDI name of the connection factory (for example, jms/ScadaConnectionFactory).
8. Confirm that XA Connection Factory Enabled is selected.
9. Click Next.
10. Click Advanced Targeting.
11. Click Create a New Subdeployment.
12. Confirm the sub deployment name matches the queue name. Select OK.
13. Select the target deployment (for example, JMSServer-1).
14. Click Finish.
15. Select the newly create connection factory on the Summary or Resources.
16. Select the Default Delivery tab.
17. Set the Default Delivery Mode to Non-Persistent.
18. Click Save.
Disabling Flex SCADA on a WebLogic Managed Server
The Flex SCADA services must only running on one active managed server at any time and should be disabled on managed servers used to service flex operations or OMA for instance.
To disable the Flex SCADA services add the following command line argument to the web logic start up command line arguments:
-Dnms.disable-flex-scada-static-service=true
Configuring Secure FEP Connections
In order to configure secure communications between the NMS system and the FEP the keystore and truststore must be configured in WebLogic.
1. Open the WebLogic Server Administration Console.
2. Select Servers and select the server hosting Flex SCADA.
3. Select Keystores.
4. Set the Keystores option to either Custom Identity and Java Standard Trust or Custom Identity and Custom Trust.
5. Enter Custom Identity Keystore location, Custom Identity Keystore Type, Custom Identity Keystore Passphrase and Confirm Custom Identity Keystore Passphrase. The custom identity keystore must contain the public and private key of the WebLogic server.
6. Enter the Trust Keystore details. If using the Java Standard Trust then the location and keystore type are automatically populated to $JAVA_HOME/jre/lib/security/cacerts. If the Java Standard keystore is held in any other location then the Custom Identity and Custom Trust option must be chosen.
The Trust Keystore must contain the Certificate Authority Certificate used to sign the FEP's public keys.
7. Click Save.
8. Select the SSL tab.
9. Enter the Private Key Alias which the private key is stored under in the Custom Identity Keystore.
10. Enter the Private Key Passphrase and Confirm Private Key Passphrase.
11. Click Save.