Configuration Tasks for the MV90 Adapter
This section describes the tasks that should be taken after installing Oracle Utilities Smart Grid Gateway MV90 Adapter, including:
Deploying the OSB Adapter for the MV90
The OSB adapter can be deployed on the bundled WebLogic example server instance or on a separate WebLogic server instance. To deploy the OSB adapter, use the following procedures.
To Deploy on the Example WebLogic Instance
1. Create the following directories under <OSB_LOG_DIR>.
mv90-usage
mv90-usage-arch
mv90-usage-error
 
2. Start the example OSB WebLogic instance.
Refer to the section Creation of Example Weblogic Domains.
UNIX
cd $SPLEBASE/osbapp
./startWebLogic.sh
 
Windows
cd %SPLEBASE%\osbapp
startWebLogic.cmd
 
3. Create JMS queues and target them to the OSB admin server.
a. Create a JMS server “OSB-JMSServer” and target it to admin server.
b. Create a JMS module “MV90-SystemModule”.
c. Under “MV90-SystemModule” create a sub-deployment “MV90-JMSFAServer” and target it to “OSB-JMSServer”.
d. Create the following JMS queues:
Queue Name: DestinationQueue-D5
JNDI Name: DestinationQueue-D5
Sub-deployment: MV90-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: NotificationQueue-D5
JNDI Name: NotificationQueue-D5
Sub-deployment: MV90-JMSFAServer
Targets: OSB-JMSServer
4. Deploy the OSB adapter on the example WebLogic instance.
For SSL deployment, please refer to the section Deploying OSB adapter on SSL.
UNIX
ccd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile
deploy-osb_MV90.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile
deploy-osb_MV90.xml
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes.
Windows
cd %SPLEBASE%\osbapp
 
%SPLEBASE%\product\apache-ant\bin\ant -buildfile
deploy-osb_MV90.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes.
Create the following JMS configuration in the Oracle Utilities Meter Data Management application Admin Server:
1. Create a JMS module “MV90-SystemModule” and target it to the Managed Server where the Oracle Utilities Meter Data Management application is running.
2. Under the JMS module, create a new Foreign Server "OSBForeignServer-D5" and accept the default targets.
3. Under the Foreign Server, navigate to the General tab and configure the following:
a. JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
b. JNDI Connection URL: URL for OSB Sever in the format - t3://<osb hostname>:<osb port number> (Use t3s for SSL)
c. JNDI Properties Credential: Credentials for user with access to OSB server
d. Confirm JNDI Properties Credential: Same as JNDI Properties Credential
e. JNDI Properties: java.naming.security.principal=<User with access to OSB server for which credentials were provided>
4. Under Destinations, create the following foreign destinations:
• Name: DestinationQueue-D5
Local JNDI Name: ForegnDestinationQueue-D5
Remote JNDI Name: DestinationQueue-D5
• Name: IMDDestinationQueue-D5
Local JNDI Name: ForegnIMDDestinationQueue-D5
Remote JNDI Name: IMDDestinationQueue-D5
• Name: NotificationQueue-D5
Local JNDI Name: ForegnNotificationQueue-D5
Remote JNDI Name: NotificationQueue-D5
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D5
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D5
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D5
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
To Deploy on a Separate WebLogic Instance
See Configuring Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Meter Data Management for more information about deploying OSB components on a separate WebLogic server.
To deploy on a separate WebLogic instance:
1. Create the following directories under <OSB_LOG_DIR>.
mv90-usage
mv90-usage-arch
mv90-usage-error
 
2. Copy the following jars to the lib folder under the WebLogic domain directory.
spl-d1-osb-25.4.jar
 
This jar is present under the following location:
UNIX: $SPLEBASE/etc/lib
Windows: %SPLEBASE%\etc\lib
3. Start the separate WebLogic instance.
4. Create JMS queues and target them to the OSB admin server:
• Create a JMS server “OSB-JMSServer” and target it to admin server.
• Create a JMS module “MV90-SystemModule”.
• Under “MV90-SystemModule” create a sub-deployment “MV90-JMSFAServer” and target it to “OSB-JMSServer”.
• Create the following JMS queues:
Queue Name: DestinationQueue-D5
JNDI Name: DestinationQueue-D5
Sub-deployment: MV90-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: NotificationQueue-D5
JNDI Name: NotificationQueue-D5
Sub-deployment: MV90-JMSFAServer
Targets: OSB-JMSServer
5. Deploy the OSB adapter on the separate WebLogic instance.
For SSL deployment please refer to the section Deploying OSB adapter on SSL.
UNIX
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile
deploy-osb_MV90.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes.
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile
deploy-osb_MV90.xml -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
Note: Use the following command if this is an upgrade from a previous version:
cd %SPLEBASE%/osbapp
%SPLEBASE%/product/apache-ant/bin/ant -buildfile
deploy-osb_MV90.xml
update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
 
This will not override any OSB custom changes.
Create the following JMS configuration in the Oracle Utilities Meter Data Management application Admin Server:
1. Create a JMS module “MV90-SystemModule” and target it to the Managed Server where the Oracle Utilities Meter Data Management application is running.
2. Under the JMS module, create a new Foreign Server "OSBForeignServer-D5" and accept the default targets.
3. Under the Foreign Server, navigate to the General tab and configure the following:
a. JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
b. JNDI Connection URL: URL for OSB Sever in the format - t3://<osb hostname>:<osb port number> (Use t3s for SSL)
c. JNDI Properties Credential: Credentials for user with access to OSB server
d. Confirm JNDI Properties Credential: Same as JNDI Properties Credential
e. JNDI Properties: java.naming.security.principal=<User with access to OSB server for which credentials were provided>
4. Under Destinations, create the following foreign destinations:
• Name: DestinationQueue-D5
Local JNDI Name: ForegnDestinationQueue-D5
Remote JNDI Name: DestinationQueue-D5
• Name: IMDDestinationQueue-D5
Local JNDI Name: ForegnIMDDestinationQueue-D5
Remote JNDI Name: IMDDestinationQueue-D5
• Name: NotificationQueue-D5
Local JNDI Name: ForegnNotificationQueue-D5
Remote JNDI Name: NotificationQueue-D5
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D5
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D5
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D5
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D5
Remote JNDI Name: weblogic.jms.XAConnectionFactory
Starting the Application
The OSB WebLogic server instance should be up and running before starting the main application.
Creating WebLogic Domain
Create the WebLogic native domain and deploy the application. For instructions refer to the Native Installation Oracle Utilities Application Framework (Doc ID: 1544969.1) document on My Oracle Support.
The MDB user configured in Menu 3 during the Oracle Utilities Application Framework installation has to be created in the Oracle Utilities Application Framework application and WebLogic console, and should be part of the “cisusers” group.
Note: The first time you start Oracle Utilities Meter Data Management, you need to log into the WebLogic console and give system access to cisusers role.
The WebLogic console application can be accessed from the following URL: http://<hostname>:<portname>/ console