SOA CS ADAPTERS - JMS

JMS ADAPTERS - Creating Weblogic Resources

JMS (Java Messaging Service) Adapter is based on JCA architecture (J2ee Connector Architecture) also known as Binding components. It can be used either as Inbound (receive message) or external (publish message).

Adapters basic helps converts native data to web services format to be used by composite. Conversion is done using JCA API, packaged as .rar file deployed in WebLogic server which is available during the runtime of a composite.

It falls under category of Technology Adapters. This can be used by both Oracle SOA Suite and Oracle Service Bus.

JMS is Java Messaging Server Application which runs of Application Servers as WebLogic provides JMS messaging infrastructure two mechanisms for message exchange –

• Point to Point (Queue)
• Publisher Subscribers (Topic)

This acts as a bi-directional adapter which allows messages to be published both (inbound and outbound)


JMS Adapter Configuration

1. Login to SOA CS instanceàClick Managed Service IconàClick WebLogic Administrative Console.
2. Login to WebLogic Admin ConsoleàExpand Domain Structure Panelà ServicesàMessagingàJMS Modules
3. Click Lock and Edit Button. We can either create a new JMS module or create a new infrastructure under an existing module like SOAJMSModule. Click this module
4. Click Newà Select Queue àClick NextàProvide Name and JNDI Name as TestQueue1 and jms/TestQueue1. Click Finish. The Queue is now created
5. Click QueueàClick Subdeploymentà(Target to SOA JMS Server)
6. Click NewàSelect Connection FactoryàClick NextàProvide Name and JNDI Name as TestCF1 and jms/TestCF1. Click Finish. The Connection Factory is now created
7. Click ConnectionFactoryàClick Subdeploymentà(Target to SOA JMS Server)
8. Expand Domain Structure Panelà Deploymentsà JmsAdapteràClick ConfigurationàClick Outbound Connection PoolàSelect Existing Connection FactoryàClick newàGive JNDI Name of ConnectionPool as eis/TestQueue1. Save the deployment plan as JMSAdapterPlan.xml
9. Go Back to the ConnectionFactory created in Step8. Click the above JNDIàProvide ConnectionFactory created in Step 6 in the ConnectionFactoryLocation field, Click Save. Finally activate changes.
10. Click Lock and Edit. Expand Domain Structure Panelà Deploymentsà Navigate to JMS AdapteràClick JMS AdapteràClick Update Button, Click the option having the deployment plan created in Step8

SOA CS Instance Provisioning

1.       Login to Oracle Cloud and Browse till classic infrastructure

a.       Once you login – the logged in cloud url will be https://console.#####.oraclecloud.com/

b.       Browse to Profile àService User Console

c.       You will enter a similar URL - ttps://myservices-cacct-####.console.oraclecloud.com/mycloud/cloudportal/cloudHome

d.       Click à Select classic infrastructure

2.       Create pre-requisites before provisioning Oracle SOA Cloud Service:

a.       Create Storage Backups for DB and SOA

                                                               i.      Click Top Left Navigation Menu à Storage ClassicàCreate ContaineràGive name (DBBackUp)

                                                             ii.      Click Top Left Navigation Menu à Storage ClassicàCreate ContaineràGive name (SOABackUp)

3.       Create Database Cloud Instance and SOA Cloud Instance

a.       Create Database Cloud Instance:

                                                               i.      Click Top Left Navigation Menu àDatabase ClassicàCreate Instance

                                                             ii.      Provide Instance Name(SOACSEEDB<UserName>) and other details as per Oracle Standards and generate the SSH Key. Download and save it to your local system.  The DB instance is now created. Provision time for this instance is almost 30 mins .

b.       Create SOA Cloud instance:

                                                               i.       Click Top Left Navigation Menu àSOA

                                                             ii.      GiveDetails. Give details of Database instance previously created and can use the public key previously generate. Provide details as per Oracle Standards and Business Needs. The SOA instance is created after 60mins.