Archive for the 'WLS' Category

Enabling Logging in Service Bus

To enable pipeline logging in Service Bus, steps remain same as below but the location where do we do this activity changed. The screenshots shown in this post

  • Enable logging in Global Settings
  • Enable logging at Pipeline level

Global Settings

Login to EM Console and navigate to SOA –> service-bus (Admin Server) as shown below.


Click on Global Settings tab and set Logging Enabled property. We can also enable Monitoring, Alerts, Reporting and Result Cache as shown below.


Pipeline Settings

In EM Console, navigate to SOA –> service-bus –> <<Service Bus Project>>.


Go to Operations tab and query for Pipelines. Here we can see all monitoring related properties for Pipelines.


Click on Pipeline and go to Properties tab to enable Logging as shown below. We can set other Monitoring and Tracing related properties as well. We can also set log level so that it will be shown in log files.


This logging information is shown in <<osbservername>>-diagnostic.log.

Another related blog entry:


FMW is released !!!

FMW was released last week and it seems to be a patch release for 12.2.1. Some quick links related to SOA are given below.






SSL using KSS

In this post, we will use KSS (Keystore Service) for SSL setup. The screenshots showed in this post are based on SOA 12.2.1 but these steps remain same for 12.1.3 as well.

Creating Application Stripe:




Creating KSS Keystore:



Creating Keypair:




Oracle recommends key size to be more than equal to 1024. If we want to get it signed by any CA, we can generate CSR by clicking Generate CSR which is recommended for Production env. But for Development purpose we can use this keystore as it is.


Clicking on alias name will bring up the following screen showing the certificate information.


Configuring 1-Way SSL:

Enable SSL port by navigating to Environment –> Severs-> Admin Sever –> General.


Go to Keystores tab. Click Change to select Custom Identity and Custom  Trust as shown below and click Save to save the changes.


Modify Custom Identity and Trust stores as shown below. observe the usage of system trust store kss://system/trust. Oracle recommends this approach to simplify the trusted certificates setup.


Go to SSL tab and give the Private key alias as shown below. Here give the password as “password” and click Save. See related note at end of this post.


Go to Advanced settings and set Hostname verification to None and also set Two way Client Cert Behavior to Clients Certs not Required as we are doing setup for 1-way SSL. This setting will enforce WLS server not to request client certificates.


Restart the server and now we should be able to access admin console using HTTPS URL like http://localhost:7002/console.

Similarly, configure OSB managed server using same Keystore or by creating a new one similar to above as shown in the following screenshots.. Restart the server after changes.




Enable HTTPS for OSB proxy service as shown below.


And now we should be able to access the proxy service WSDL using HTTPS URL like https://localhost:7008/entity/CustomerService?wsdl

Refer to this post for 2-way SSL setup and follow below steps to import the certificate into trust store.





Note that KSS does not support certificate in binary format which is the default encoding used by JKS. We can use –rfc option of keytool command to export the certificate into printable encoding format as shown below.

keytool -export -keystore .\soakeystore.jks -file cert.cer -alias localsoa -rfc


When no Private Key Passphrase is mentioned in the SSL tab, em console is not accessible and following errors are shown in the log.




I will use this post as a repository of useful links and blogs which I can expect to grow exponentially over the time, so will try to include links on more generalized or important topics of much interest.

– SOA Suite PS6 New Features


– SOA SDLC by Mark Nelson


– Understanding View Accessors


-12c JMS Adapter Scalability


Cluster Messaging Protocols


– Multiple SOA Suite Revisions with DB Adapter


– Message Sequencing Patterns (white paper)

– Parallel Routing Rules


BPEL Mania

List of All Instance States

– Transaction Boundaries and Rollbacks

Fault Handling

OTN Article Series

Fault Handling in SOA Suite – Advanced Concepts

Business Rules

Self-Study Course


EDN Debugging

– Fanning out Events

– SOA 12c – EDN Articles

Continuous Integration

Deploy SOA Composites using Hudson


Best Practices

– 11g Hands-on Tutorial

– WLST Fundamentals in context of OSB

– Working with Oracle Security Token Service

– One-Way Authentication Policies in OSB

– Coherence Integration

– Caching Strategies for OSB 11g

Out-of-Process Coherence Servers

– 12c Hands-on Tutorial

12c – Series of Articles

– 12c – REST enabling SOA


Oracle Blog


    BPM vs BPEL

     Case Management

Quick Series

Case Activities, Part-I

SOA Governance

 – SOA Governance Through Enterprise Architecture

Fusion Applications

 Fusion Applications Life Cycle

 – Request Flow in Fusion Applications

 – Asynchronous Web Services in Fusion Applications

 – Oracle Fusion DOO – Integrating External Systems using EIL


   – Translating Customizations

ADF-BC Service

Recently started looking into Fusion Applications, where ADF BC Services are used at the Data Service layer rather than DB adapter. Lot of articles are found and there is nice documentation as well on how to create the ADF-BC services. I just want to highlight following points as It might take a little while to figure out for novices. And  the existing SOA domain ( did not enforce any additional runtime/libraries installation for deploying ADF-BC services EAR file .

  • Typical ADF-BC service URL looks like ://http://<host>:<port>/<context-root>/<servicename>.  Context Root should be mentioned in Project Properties –> Java EE Application –> Java EE Web Context Root and always give a meaningful name instead of the default value.


  • And service name is the one given while exposing the application module as the service and it’s not Application Module name.


  • By default, AM uses JNDI of data source in specific format as shown below. If we want to use existing data source make sure that it’s modified to your data source JNDI and not JNDI of DB connection pool.


  • Also make sure you uncheck ‘Auto Generate’ option in application deployment profile(EAR) if existing data source has to be used and does not want to create data sources defined in AM.


Weblogic Smart Patch

Recently, i had to apply a patch recommended by Oracle to disable ESS to my local Weblogic 10.3.6 installation. Not being a admin made me to go through the documentation to find out the process is very simple.

We have to just issue the following command in command window, after navigating to the directory MW_HOME/utils/bsu

bsu -prod_dir=C:\Oracle\Middleware\FMW11116\wlserver_10.3 -patchlist=KZKQ -verbose -install

Related documentation link.

Extending the Weblogic Domain

In this post, I quickly show you how to extend an existing weblogic domain which is quite simple and straight forward. Initially i have OSB domain and extended the same domain to include SOA.

Open the configuration wizard (config.cmd) from $MW_HOME/wlserver_10.3\common\bin and select the option as shown below and click on Next.


Select the domain directory from the selection browser.


Choose the products from the displayed list.


Give database schema details for new components that get added because of the selection in the previous screen. For example, in the current scenario the component schemas ‘SOA Infrastructure’ , ‘User Messaging Service’ and ‘SOA MDS Schema’ have to modified with correct database information as shown below and click on Next.


Make sure that connection is successful by observing the logs shown and click on Next twice.


Verify the configuration summary and click on Extend button to finish.


Once the domain is created, click on Done button and bring up the server to verify the installation of SOA server by opening the EM console and look for soa_infra.


Managed Server Start issue

Getting the following error while starting the managed server. The admin server has been started successfully without any issues.

<13 Aug, 2011 10:58:41 PM IST> <Error> <Security> <BEA-090783> <Server is Runnin
g in Development Mode and Native Library(terminalio) to read the password secure
ly from commandline is not found.>

The issue has been resolved by setting WLS_USER and WLS_PW in startManagedWeblogic.cmd as shown below:




Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 353 other followers

Enter your email address to follow this blog and receive notifications of new posts by email.