In this post, we will see creation of Service Bus application and projects using maven archetypes. And we will use local Maven Repository for demonstration.
Generate Service Bus Application and Project as shown below.
Import this maven project in JDeveloper using the steps mentioned below. Select File –> Import and select Maven Project option and click OK.
Open application level POM file in Application Resources directory as shown below and observe the details.
Open project level POM file and observe the details.
Open System level POM file and observe the details.
Add plugin and other server details in project level POM files (both System and Service Bus Project) as shown below. Remember using the Admin Server port as the server url.
You can generate the sbar file for your Service Bus Projects using mvn package (from directory of Service Bus Application) and can be found in <<project>>/.data/ maven.
Deploy your Service Bus projects using mvn pre-integration-test (from Service Bus application directory).
You can execute Service Bus Plugin goals in following manner from directory containing project POM file.
In this post, we will see creation of SOA application/projects using the maven archetypes. And we will use local Maven Repository for the demonstration.
Navigate to %MW_HOME%\oracle_common\plugins\maven\com\oracle\maven\oracle-maven-sync\12.1.3 and use following commands to sync your local repository:
Import this maven project in JDeveloper using File –> Import and select the Maven Project option as shown below. Click OK.
Give your application directory as Root Directory which brings up all POMs and select other options as shown below. Click OK.
Enter Application Name and click OK.
Click OK if you get any error related to overriding the existing project dialog so that jws file is created. Now your project explorer should look like as below.
Open application level POM file in Application Resources directory as shown below and observe the details.
Open project level POM file in Resources directory of SOA Project and observe the details.
Compile SOA Application using mvn compile (from directory of SOA Application).
Modify server details in project level POM file as shown below and deploy your SOA projects using mvn pre-integration-test (from SOA application directory).
After execution, you will see following output and also can observe the SOA project deployed to SOA server as shown below.
You can execute SOA Plugin goals in the following manner from the directory containing project POM file.
Oracle recently released Maven Repository which is a giant leap in adopting Maven too for building, packaging and deploying SOA, ADF applications. You can access the repository here. To access this, you should be registered user with Oracle and accept the licensing terms.
In this post, we will see how to setup Archiva repositories and populate it with artifacts from Oracle Home. You can refer to Oracle FMW Continuous Integration documentation here for more information.
You can download the latest version of Archiva from here and corresponding documentation can be found here.
Archiva installation is so simple and you have to just unzip file contents. The standalone distribution comes up with bundled jetty server. By default, the server uses port 8000. You can always change this port to your desired value as shown below by modifying jetty.xml in conf directory.
Navigate to bin directory and start the server using the following command:
archiva console
Once the server started, launch archiva using url http://localhost:8088. The first step is to create the admin user as shown below, so CreateAdmin User on the page launched. Enter the password and email and do Save.
Now login using Admin credentials and navigate to Repositories which shows 2 default repositories as shown below.
By default, the internal repository is for maintaining the fixed-version released artifacts includes finished versions of artifacts, versions that are no longer in development, and released versions. And the snapshot repository holds the work-in-progress artifacts denoted with a version having suffix SNAPSHOT, and artifacts that have not yet been released.
Here, we will create repositories keeping development environment in mind. It’s always recommended to create different repositories for DEV, QA and PROD as there is possibility of having different versions of same artifacts. For our purpose, we will reuse the snapshots repository and create 2 repositories mirror and dev. The mirror repository is used to cache third-party proxied artifacts and dev is used similar as internal repository.
Navigate to Repositories link and click Add. Set the properties similar to below.
Click Save to go back to Managed Repositories page as shown below and here you can observe the new mirror repository.
Create dev repository in similar way and make sure that you uncheck Block Redeployments as shown below.
Archiva has a provision to create Repository Groups, that allows to specify single URL instead of multiple repository URLs when we are using more than 1 repository.
Here we will create a repository group dev-group consisting of all the above. Navigate to Repository Groups and click Add.
Give the name as dev-group and drag dev, snapshots and mirror repositories from Available list to left as shown below.
Click Save and observe the repository group as shown below.
Archiva uses proxy connector to link local repository with a remote repository. So when a request is received by repository, the connector decides whether it should request artifact from remote repository and cache the result locally for future requests.
By default, internal repository is connected to remote repository using Proxy Connector. This you can observe by navigating to Proxy Connectors as shown below.
Since we want our mirror repository to proxy remote repository, delete the existing proxy connector. Click Add and create new Proxy Connector as shown below. Observe that Managed Repository is selected as mirror. Click Save.
With this, you have finished setting up required Archiva repositories.
By default, Oracle FMW installation comes up with Maven 3.0.5 and is available in following location. So set M2 and M2_HOME system variables accordingly.
Use the following as your user specific maven settings. Remember to modify the passwords in server elements.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
In this post, I just want to present an idea on how to make Service Bus work with EDN in SOA Suite 12c. For demonstration purpose, I will consider Durable Subscriber functionality introduced in 12c.
You can download the SOA and Service Bus projects here and here.
My setup includes 2 business events Create Order and Update Order and have the following durable subscribers created because of SOA Composites. Refer to these articles for more information on EDN. Note that, Client ID is different as mentioned below based on the consistency level used for the event subscription.
For Guaranteed -> edn_wljsm_localtx_client
For OneandOnlyOne -> edn_wljsm_xa_client
Main idea is to create a durable subscriber for our Proxy Service similar to the ones shown below. So note down Client ID and Message Selector shown below and use it in our Proxy Service configuration. Here we are subscribing our Proxy Service to Create Order business event.
Now create Proxy Service and set Endpoint URI in Transport tab as shown below. EDN uses EDN Topic for storing and delivering the EDN messages to subscribers.
Give the Message Selector and Client ID noted in previous step in Transport Details tab as shown below and select Durable Subscription option.
Deploy you Service Bus project and observe that another durable subscriber has been created for Proxy Service as shown below.
To make sure that things are working as expected, push the message read by Proxy service to other JMS queue. Here I created queue named CustomJmsQ and following screenshot shows no messages are pushed yet.
Raise the Create Order business event from SOA Composite. And you can observe that message payload have been inserted into JMS queue.
Shut down OSB managed server and observe status of durable subscriber. As shown below the Active status is shown as false indicating that Proxy service is not longer ready to accept messages.
Again raise the Create Order business event. And now you can observe that message is shown in Current Count means not yet delivered to Proxy Service.
Now restart your OSB managed server navigate to CustomJmsQ. Now you can observe 2 messages in this queue including the latest one as shown below.
Now Un-deploy Service Bus project. And you can observe that corresponding durable subscriber is deleted too.
Remember the following:
EDN bus comes with SOA server, so you may not be able to use EDN in OSB only deployments.
Since there is no native support for business events in service bus, we will not be able to set any consistency levels and even the retry would not happen similar to SOA composites.
Here we directly gave Endpoint URI of Proxy Service to point to EDNTopic residing different server. Ideally, you may have to go for foreign server.
Finally, I have not verified the same with client edn_wlsjms_xa_client. Please let me know in comments when you try.
Siva's Blog 