How to run and debug Oracle Service Bus 12c services on the Integrated Weblogic Server

27Jun

After developing a Service Bus project in JDeveloper 12c we can deploy it on the internal Weblogic server.
In this blogpost we use the HelloWorld service build earlier as example.

If this is the first time you execute the integrated Weblogic server you will get a pop-up to configure the domain.

Starting the Integrated Weblogic server for the 1st time takes a looooooooot of time, but eventually it is RUNNING and a panel with the look-and-feel of the classic Oracle Service Bus 11g is there.

We can set the SOAP message payload here to debug/test our service.
Since our HelloWorld example ignores any request message, so we can keep the request as-is and by pressing Execute we make the service call to our pipeline.

By checking the Invocation Trace we can debug our service call and check if our service is functioning as expected.

Since we are know running a Oracle Weblogic domain with the SOA/OSB extensions deployed, we can take a quick look at the console.
The most interesting ones are located here (change the port if the default port 7101 was not used creating the domain):

Looking at the Enterprise Manager we see there is a dedicated service-bus and soa-infra part still seperating both components logically.

The biggest change however is the sbconsole which was there since the days of BEA Aqualogic Service Bus.
Changes are not always bad, however it will probably take me a while to get used to it. :)
But mostly determine where certain part of the administration & configuration of services can take place, either in EM or SBCONSOLE.

One response to “How to run and debug Oracle Service Bus 12c services on the Integrated Weblogic Server”

Diksha

11-06-2015 at 22:52

Hi,
I have configured the integrated server as you mentioned.However when i m trying to access http://localhost:7101/servicebus/
I am getting following error
rror 401–Unauthorized
From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1:
10.4.2 401 Unauthorized

The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11.