9. Configure AQ-JMS Bridge

The following steps are to be performed to configure the AQ-JMS Bridge through the Weblogic Console:

• Create Data Sources for AQ-JMS Bridge
• Configure MDB Flow
• AQ-JMS Topic Setup
• Create Credentials and System Policies
• Deploy MDB EJB

Note

Ensure that MDB EJB is not configured and deployed (i.e. OfsllAppQueue.ear deploy­ment) on the same server on which the other WebServices are deployed.

9.1 Create Data Sources for AQ-JMS Bridge

1. Login to Oracle Weblogic 12c console (http://hostname:port/console).

   

2. On successful login, the following window is displayed.

   

3. Click Domain Name > Services > Data Sources. The following window is displayed.

   

4. Click ‘Lock & Edit’ button on the left panel. Click ‘New’ on right panel and select ‘Generic Data Source’.

   

5. The following window is displayed.

   

6. Specify the following details:

• Enter Data source Name
• Enter the JNDI Name as ‘jdbc/aqjmsdb’.

Note

If required, you can specify any other JNDI name, but however ensure to use the same JNDI name during other configuration steps.

• Select ‘Oracle’ as Database Type.

7. Click ‘Next’. The following window is displayed.

   

8. Select the Database Driver ‘Oracle's Driver(Thin XA) for Services connections;Versions:Any’.
9. Click ‘Next’. The following window is displayed.

   

10. Click ‘Next’. The following window is displayed.

    

11. Enter the Database details.
12. Click ‘Next’. The following window is displayed.

    

13. Click ‘Test Configuration’. On completion, displays a confirmation message as ‘Connection test succeeded’.
14. Click ‘Next’. The following window is displayed.

    

15. Select target Server as ‘OFSLLREL_ManagedServer’.
16. Click ‘Finish’ to activate the changes.

Update the following parameters in JDBC data source connection pool:

1. Select Services > Data Sources > select the AQ_JMS_DB data source > Connection Pool.
2. Initial capacity and Maximum capacity is defaulted to 30, if the number of concurrent users are more this needs to be increased.

9.2 Configure MDB Flow

To configure the MDB Flow from Weblogic Console, do the following:

1. Login to Oracle Weblogic 12c console (http://hostname:port/console).
2. On the left pane, click 'Services'.
3. In Messaging tree click ‘JMS Modules’. The following window is displayed.

   

4. Click 'New'. The following screen is displayed.

   

5. Specify the following details:

• Name: AQJMSModule
• Descriptor File Name: AQJMSModule

6. Click ‘Next’. The following window is displayed.

   

7. Select target servers as ‘OFSLLREL_ManagedServer’.
8. Click ‘Next’. The following window is displayed.

   

9. Click ‘Finish’ to activate the changes. The following window is displayed.

   

10. Click on the JMS Module that you created. The following window is displayed.

    

11. Click ‘New’ in ‘Summary of Resources’ section. The following window is displayed.

    

12. Select ‘Foreign Server’ as the option for type of resource to be created and click ‘Next’. The following window is displayed.

    

13. Specify the name of the Foreign Server as ‘AQForeignServer’ and click 'Next'. The following window is displayed.

    

14. Click ‘Finish’ and activate the changes. The following window is displayed.

    

15. Click on the Foreign Server that you created. The following window is displayed.

    

16. Specify the following details:

• Enter JNDI Initial Context Factory as ‘oracle.jms.AQjmsInitialContextFactory’.
• JNDI Properties as ‘datasource=jdbc/aqjmsdb’.
• Ensure ‘Default Targetting Enabled’ option is selected.

17. Click ‘Save’.
18. Select ‘Destinations’ Tab and click ‘New’ to create new destination. The following window is displayed.

    

19. Specify the following details:

• Name: AQJMSQueue
• LocalJNDI Name: /jms/aq/OfsllQueue
• Remote JNDI Name: Queues/OFSLL_OUTBOUND_Q

20. Click ‘OK’ and save the changes.
21. Select ‘Connection Factories’ Tab and click ‘New’ to add new connection factory. The following window is displayed.

    

22. Specify the following details:

• Name: AQofsllCF
• Local JNDI Name: /jms/aq/OfsllCF
• Remote JNDI Name: XAQueueConnectionFactory

23. Click ‘OK’ and save the changes.

9.3 AQ-JMS Topic Setup

AQ-JMS Topic Bridge facilitates for group publishing to set of subscribed users. In a configured setup, a published message is sent to all the interested subscribers. Accordingly zero to many subscribers will receive a copy of the same message.

9.3.1 Create AQ-JMS Topic Bridge

To configure the AQ JMS Topic from Weblogic console, do the following:

1. Login to Oracle Weblogic 12c console (http://hostname:port/console).
2. On the left pane, select Services > Messaging > JMS Modules. The following window is displayed.

   

3. Click 'AQJMSModule'. The following window is displayed.

   

4. In the Summary of Resources section, click 'New'. The following window is displayed.

   

5. Select 'Foreign Server' as the option for type of resource to be created and click 'Next'. The following window is displayed.

   

6. Specify the name of the Foreign Server as ‘OfsllTopicFS’ and click 'Next'. The following window is displayed.

   

7. Click 'Finish' and activate the changes. Once done, the following window is displayed.

   

8. Click on the Foreign Server that you created. The following window is displayed.

   

9. Specify the following details and click 'Save'.

• Enter JNDI Initial Context Factory as 'oracle.jms.AQjmsInitialContextFactory'.
• JNDI Properties as 'datasource=jdbc/aqjmsdb'.
• Ensure 'Default Targetting Enabled' checkbox is selected.

10. Select 'Destinations' tab and click 'New' to create new destination. The following window is displayed.

    

11. Specify the following details and click 'OK' to save the changes.

• Name: AQJMSTopic
• LocalJNDI Name: /jms/aq/OfsllTopic
• Remote JNDI Name: Topics/OFSLL_OUTBOUND_TOPIC

12. Select 'Connection Factories' tab and click 'New' to add new connection factory. The following window is displayed.

    

13. Specify the following details and Click 'OK' to save the changes.

• Name: AQJMSTopicCF
• Local JNDI Name: /jms/aq/OfsllTopicCF
• Remote JNDI Name: XATopicConnectionFactory

9.4 Create Credentials and System Policies

In order Configure MDB flow, you need to create credentials and system policies. The credentials are accessed through CSF framework which is managed by Oracle Weblogic Server. The keys are managed by Maps and Maps need to be given with Permissions.

1. Login to Oracle Enterprise Manager (http://hostname:port/em).
2. On the left panel, right click on OFSLL_domain and select Security > System Policies > Credentials. The following window is displayed.

   

3. Click ‘Create Map’. The following window is displayed.

   

4. Enter Map Name as ‘ofsll.int.bureau’ and click ‘OK’.
5. Click ‘Create Key’. The following window is displayed.

   

6. Specify the following details:

• Select Map as ‘ofsll.int.bureau’ from the drop down list.
• Specify Key as ‘jdbc_ds_key’
• Select Type as ‘Generic’ from the drop down list.
• Specify the Credential as ‘jdbc/aqjmsdb’

7. Click ‘OK’.
8. Similarly you need to create the following Maps and corresponding keys as indicated in following table.

   Maps	Keys	Description
   ofsll.int.bureau		This map is used to setup keys for all credit bureau interfaces
   	ProxyServer	Name of the proxyServer to be configured
   	ProxyPort	Port to which ProxyServer is running.
   	ExpEcalsURL	The Experian Connection URL to be config­ured.
   	ExpDirectExperianEna­bled	If you set value as true, then you would be set­ting ecals response URL. Else, the Ecals request URL
   	ExpCertPath	The location of .jks file which contains the valid certificate for Experian Credit Bureau.
   	ExpBusUserNamePass­word	Login Credentials to be configured for Experian Business reports.
   	ExpConUserNamePass­word	Login Credentials to be configured for Experian Consumer reports.
   	EfxURL	The Equifax Connection URL to be configured.
   	EfxCertPath	The location of .jks file which contains the valid certificate for Equifax Credit Bureau.
   	EfxUserNamePassword	Login credentials to be configured for access­ing Equifax Reports.
   	TucCertPath	The location of .p12 file which contains valid certificate for Transunion Bureau .
   	TucCertPassword	The password that requires to read the valid .p12 certificate for the Transunion Bureau.
   	TucUserNamePassword	Login credentials to be configured for access­ing Transunion reports
   	TucConnectionURL	The Transunion URL to be configured.
   	jdbc_ds_key	Datasource configured to retrieve data for bureau.
   	source	Configured as EXTERNAL for actual call.
   ofsll.int.outbound		This map is used to setup keys for the Route­One and Dealer track call back from OFSLL.
   	roUserNamePassword	Login Credentials used at the time of call back from OFSLL to RouteOne Interface.
   	dtUsernamePassword	Login Credentials used at the time of Call back from OFSLL to Dealer Track Interface.
   	jdbc_ds_key	Datasource configured to retrieve data for out­bound Resources.
   ofsll.int.bip		This Map is used to setup all the Keys required to setup interface with BIP to generate reports.
   	local_top_dir	Define the path of the local BIP server where you would like place the generated BIP reports.
   	email_from_addr	Define the From Email address to be used while sending email for the generated BIP reports.
   	emailBodyContentPath	The path for ‘file.properties’ file that contains the content of the subject and body required while sending letter, report or correspondence as mail to the applicant or producer. For example; /tmp/file.properties *Refer to note below for details on ‘file.proper­ties’ file creation for email configuration.
   	fax_server	Configure the name of Fax server to be used to fax the generated BIP reports.
   	jdbc_ds_key	Datasource configured to retrieve data for BIP.
   ofsll.int.filetransfer		This map is used to setup keys for all credit bureau interfaces
   	sftp_key	Credentials to login to SFTP server(Username/Password)
   	sftp_top_dir	Top root directory for SFFTP server
   	sftp_servers	SFTP server names
   ofsll.int.security	bip_key	This is BIP login credentials
   ofsll.int.gri	GriURL	GRI web service URL to be configured.
   	GriAPIKey	GRI API key to be configured
   	ProxySet	System Level Proxy Enabled/Disabled. Value can be either true or false. True= proxy required False = proxy not required
   	ProxyHost	Name of the proxyServer to be configured. Set only if ProxySet =true.
   	ProxyPort	Port on which ProxyServer is running. Set only if ProxySet =true.
   	jdbc_ds_key	Datasource configured to retrieve the request XML for GRI.
   	GriCertPath	The location of .jks file which contains the valid certificate for GRI. Configure only when a valid certificate is availa­ble.
   ofsll.int.common		This map is used to setup keys for common JMS Queue
   	OfsllJMSQueueJNDI	The JMS queue JNDI name to be configured
   	OfsllJMSQueueCF	The JMS queue connection factory to be con­figured
   	OfsllJMSServerURL	The JMS server url to be configured. Ex: t3://<JMS server host>:<JMS server port>

* A new file(file.properties) needs to be created and copied to the application server in the same path as mentioned in the value corresponding to the key 'emailBodyContentPath' under the map 'ofsll.int.bip'. The file should have the following contents:

• letter_subject='Text that is configurable and would be the subject of the mail'
• letter_body='Text that is configurable and would be the body of the mail'
• correspondence_subject='Text that is configurable and would be the subject of the mail'
• correspondence_body='Text that is configurable and would be the body of the mail'
• report_subject='Text that is configurable and would be the subject of the mail'
• report_body='Text that is configurable and would be the body of the mail'

9. On the left panel, right click on OFSLL_domain and select Security > System Policies. The following window is displayed.

   

10. Click ‘Create’. The following window is displayed.

    

11. Enter the codebase as ‘file:${domain.home}/lib/OfsllCommonCSF.jar’
12. Click ‘Add’. The following window is displayed.

    

13. Select the check box 'Select here to enter details for a new permission'.
14. Specify the following details as the first permission class.

    Permission Class	Resource Name	Permission Actions
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.bureau,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.filetransfer,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.outbound,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.bip,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.gri,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapName= ofsll.int.common,keyName=*	read
    oracle.security.jps.service.cred­store.CredentialAccessPermission	context=SYSTEM,mapN­ame=ofsll.http.listener.jndi,key­Name=*	read

15. Click ‘OK’.

9.5 JMS Queue Configuration

JMS queue is used to hold webservice invocation exception messages. It provides a mechanism for third parties to handle communication related failures.

Perform the following steps to configure JMS queue in application server.

• Create JMS Server
• Create JMS Modules
• Subdeployment
• Create JMS Queue
• Create JMS Connection Factory

9.5.1 Create JMS Server

1. Login to WebLogic Server 12c console (http://hostname:port/console). The following screen is displayed.

   

2. Specify the Weblogic administrator user name and password and click 'Log In'. The Oracle Weblogic home page is displayed.

   

3. Click Domain Name > Services > Messaging > JMS Server.
4. In the main window, click 'Lock & Edit'. The following window is displayed.

   

5. Click 'New'. The following window is displayed.

   

6. Specify the JMS Server Name as ‘OfsllJMSServer’. Click ‘Next’, the following window is displayed.

   

7. Select 'None' as the Persistent Store type. Click 'Next', the following window is displayed.

   

8. Select the target managed server and click 'Finish'.

   

9. Click 'Activate Changes' under Change Center. Once done, the following window is displayed:

   

9.5.2 Create JMS Module

1. Login to WebLogic Server 12c console (http://hostname:port/console) by specifying the Weblogic administrator user name and password.
2. Click Domain Name > Services > Messaging > JMS Modules. The following window is displayed.

   

3. Click 'New'. The following screen is displayed.

   

4. Specify the following details:

• Enter the System Module Name as ‘OfsllJMSModule’
• Enter the Description File Name as ‘OfsllJMSModule’

5. Click ‘Next’. The following screen is displayed.

   

6. Select the target server and click 'Next'. The following window is displayed.

   

7. Click 'Finish' to save and activate the changes. Once done, the following window is displayed.

   

9.5.3 Subdeployment

1. Login to WebLogic Server 12c console (http://hostname:port/console) by specifying the Weblogic administrator user name and password.
2. Click Domain Name > Services > Messaging > JMS Modules. The main window displays the list of JMS modules available.
3. Select the created JMS module ‘OfsllJMSModule’ and click 'Subdeployments' tab. The following window is displayed.

   

4. Click 'New'. The following screen is displayed.

   

5. Specify the Subdeployment Name as ‘OfsllJMSSD’. Click 'Next', the following window is displayed.

   

6. Select the check box against the newly created JMS Server and click ‘Finish’. Once done, the following window is displayed.

   

9.5.4 Create JMS Queue

1. Login to WebLogic Server 12c console (http://hostname:port/console) by specifying the Weblogic administrator user name and password.
2. Click Domain Name > Services > Messaging > JMS Modules. The main window displays the list of JMS modules available.
3. Select the newly created JMS module ‘OfsllJMSModule’. The following window is displayed.

   

4. Click ‘New’. The following window is displayed.

   

5. Select the 'Queue' option and click 'Next'. The following window is displayed.

   

6. Specify the following details while creating new JMS System Module Resources:

• Enter the Name of the Queue as 'OfsllJMSQueue’
• Enter the JNDI Name as 'jms/OfsllJMSQueue’
• Select the Template as 'None'

7. Click 'Next'. The following window is displayed.

   

8. Click ‘Finish’ to save and activate the changes. Once done, the following window is displayed.

   

You can further click 'New 'to create more Queues and repeat the steps explained above.

9.5.5 Create JMS Connection Factory

1. Login to WebLogic Server 12c console (http://hostname:port/console) by specifying the Weblogic administrator user name and password.
2. Click Domain Name > Services > Messaging > JMS Modules. The main window displays the list of JMS modules available.
3. Select the newly created JMS module ‘OfsllJMSModule’. The following window is displayed.

   

4. Click 'New’. The following window is displayed.

   

5. Click 'Next'. The following window is displayed.

   

6. Select 'Connection Factory' option and click 'Next'. The following window is displayed.

   

7. Specify the following details:

• Enter the Name of the Connection Factory as 'OfsllJMSCF’
• Enter the JNDI Name as ‘jms/OfsllJMSCF’
• Select the check box 'XA Connection Factory Enabled'

8. Click 'Next'. The following window is displayed.

   

9. Click 'Advanced Targeting'. The following window is displayed.

   

10. Select the Subdeployments as ‘OfsllJMSSD’ from the drop down list.
11. Under JMS Servers, select the check box against 'ofsllJMSServer'.
12. Click 'Finish' to save and activate the changes. Once done, the following window is displayed.

    

9.6 Deploy MDB EJB

1. Login to Web Logic application server enterprise manager (e.g.:http://hostname:port/em)

   

2. Enter valid login credentials. The following window is displayed.

   

3. Click ‘Deployment’ in the left panel.
4. Select ‘Lock & Edit’ option in the lock drop-down list available in the header. The following window is displayed.

   

5. Select ‘Deploy’ from the Deployment drop-down list. The following window is displayed.

   

6. The following window is displayed.

   

7. Browse to the folder containing the MDB EJB. Eg: C:/OfsllQueueApp.ear
8. Click ‘Next’. The following window is displayed.

   

9. Select the server on which the MDB EJB needs to be deployed.
10. Click ‘Next’. The following window is displayed.

    

11. Select the option ‘Install and start application (servicing all requests)’.
12. Check the context root and click ‘Next’.The following window is displayed.

    

13. Click ‘Deploy’. On successful deployment, the following window is displayed.

    

14. Click ‘Close’. Post deployment, you need to activate the changes by selecting ‘Active Changes’ option from ‘Edit Session’ drop-down list as indicated in step 4 above.

Note

While starting the ‘OFSLLREL_ManagedServer’, always start with option ‘-DUseSun­HttpHandler=true’ to enforce the weblogic server to uses SUN SSL implementation.