The following steps are to be performed to configure the AQ-JMS Bridge through the Weblogic Console:
Note
Ensure that MDB EJB is not configured and deployed (i.e. OfsllAppQueue.ear deployment) on the same server on which the other WebServices are deployed.
Note
If required, you may specify any other JNDI name, but ensure to use the same JNDI name during other configuration steps.
Update the following parameters in JDBC data source connection pool:
Similarly create ‘QueueAppDS’ data sources which is used by MDB for all database related operations by following the steps mentioned in above section (Create Data Sources for AQ-JMS Bridge).
Do not perform the JDBC data source update and instead follow the below steps to configure the created ‘QueueAppDS’ data source:
To configure the MDB Flow from Weblogic Console, do the following:
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.
To configure the AQ JMS Topic from Weblogic console, do the following:
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.
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 configured. |
|
ExpDirectExperianEnabled |
If you set value as true, then you would be setting ecals response URL. Else, the Ecals request URL |
|
ExpCertPath |
The location of .jks file which contains the valid certificate for Experian Credit Bureau. |
|
ExpBusUserNamePassword |
Login Credentials to be configured for Experian Business reports. |
|
ExpConUserNamePassword |
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 accessing 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 accessing 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 RouteOne 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 outbound Resources. |
|
roPostDealerUsernamePasswd |
Credentials required to upload the dealer details to Route One Portal |
|
roPostDealerWbsURL |
Route One Post Dealer Web Service url |
|
roDealerUploadURL |
Route One URL to upload the Dealer details |
|
dtPostDealerUsernamePasswd |
Credentials required to upload the dealer details to Dealer Track Portal |
|
dtPostDealerWbsURL |
Dealer Track Post Dealer Web Service url |
|
dtDealerUploadURL |
Dealer Track URL to upload the Dealer details |
|
VertexUserNamePd |
Credentials required to connect to VERTEX web service |
|
VertexTrustedId |
ID required to connect to VERTEX web service |
|
TorqueItsUserNamePassword |
Credentials required to connect to TorqueIts web service |
|
TorqueItsURL |
TorqueIts Decision service URL |
|
ProxyHost |
Name of the proxyServer to be configured. |
|
ProxyPort |
Port to which ProxyServer is running. |
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.properties’ 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 available. |
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 configured |
|
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:
Permission Class |
Resource Name |
Permission Actions |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.bureau,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.filetransfer,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.outbound,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.bip,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.gri,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.int.common,keyName=* |
read |
oracle.security.jps.service.credstore.CredentialAccessPermission |
context=SYSTEM,mapName=ofsll.http.listener.jndi,keyName=* |
read |
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.
You can further click 'New 'to create more Queues and repeat the steps explained above.
Note
While starting the ‘OFSLLREL_ManagedServer’, always start with option ‘-DUseSunHttpHandler=true’ to enforce the weblogic server to uses SUN SSL implementation.