Support to Retrieve or set a HTTP header in Oracle SOA Suite 11.1.1.5 version

Oracle SOA Suite 11.1.1.6 version provides the support to retrieve or set a HTTP header from BPEL

The same fix has been applied to the version 11.1.1.4 as a patch 12928372 but the patch was not available for the version 11.1.1.5.

Recently oracle has released the patch 12928372 for the version 11.1.1.5 also.

The patch can be downloaded for the metalink by specifying the patch no as 12928372.

 This functionality is working only with the BPEL version 2.0, make sure the BPEL process version is 2.0 when we are trying to implement this functionality.

Could not find registry for application_JBOServiceRegistry while deploying the composite with Oracle ADF-BC adapter

Could not find registry for application_JBOServiceRegistry while deploying the composite with Oracle ADF-BC adapter

When we are invoking the Oracle ADF-BC service from our Oracle SOA Suite composite, we may receive the error

“Could not find registry for applicationname_JBOServiceRegistry”.

The error is due to the wrong registry name used in the ADF-BC adapter configuration also the missing listener entry in the weblogic-application.xml

Follow the below steps to resolve the issue:

Verify the registry name provided in the ADF-BC adapter used in the composite.

The Registry name should be of form <application name>_ JBOServiceRegistry
The application name can be found on the application deployment profile of the ADF-BC application.

Invoking a ADF-BC service from the SOA Composite – Oracle SOA Suite

Invoking a ADF-BC service from the SOA Composite – Oracle SOA Suite

This blog explains how to create a sample Oracle ADF-BC service and invoke the same from the Oracle SOA Suite composite.

Creating the ADF-BC application: 

This is a simple ADF-BC application to perform the operations on the Employee table.

• Create the ADF Model Project and name it as EmpModel

 

• Select the ADF Business Components in the Project Technologies

•  Right click on the Project -- >Select ADF Business Components -- >Click on Business Components from Tables

Selective tracing for Oracle SOA Suite

Selective tracing for Oracle SOA Suite:

In a production system, setting the trace at a fine-grained level can result in a large amount of output that must be diagnosed. You can alternately use selective tracing that provides a way to get a detailed, on-disk trace selectively (for example, by user name, thereby eliminating trace output for other users).

In Oracle SOA Suite 11g:

Activate the selective tracing:

• Right-click the domain under WebLogic Domain and choose Logs > Selective Tracing.

Restrict the access to SOA Composite Service based on the User Role (Authorization to the SOA Composite Service) – Oracle SOA Suite 11g

Restrict the access to SOA Composite Service based on the User Role (Authorization to the SOA Composite Service) – Oracle SOA Suite 11g

Sometimes we may need to restrict the access to the SOA composite service based on the user role.

HTTP basic authentication and an authorization policy can be used to ensure that access is only granted to users who are members of a particular role.

This blog will explain the steps to enable authorization to our composite service. 

Configure the Users and Group:

• Login to the Weblogic console ('http://<host>:<port>/console')

• In the left menu select 'Security Realms'

• Select the realm where you want to create the users and groups.  The default is 'myrealm'

• At the top select the 'Users and Groups' tab

• Select User tab and Click 'New' and enter your user name and pwd.  Here am creating the user albin and albin1, create as many users as you want

• Select ‘Groups’ tab and create a new group.  Here I am creating  ‘IntegrationGroup’

• Go back to the users and click on  'Albin'

• Select the 'Groups' tab and add ‘IntegrationGroup’.  The user albin1 will not be part of this group.

Configure the Application Role:

• Login to EM console

• Right Click on WebLogic Domain -- >Select Security and Click on Application Roles

•  Click on 'Create' to configure a new Application Role

Invoking a web service from the composite with HTTP Basic authentication – Oracle SOA Suite

Invoking a web service from the composite with HTTP Basic authentication  – Oracle SOA Suite 11g

Sometimes we may need to invoke the HTTP Basic authentication enabled web service from the  Oracle SOA Suite composite.

This blog will explain the steps to invoke the web service with the HTTP basic authentication enabled.

Configure the credential store:

The credential should be configured in the credential store to invoke the web service with the HTTP Basic authentication enabled.

If the credential store is not configured already then follow the below steps to do the same.

• Login to EM

• Right Click on WebLogic Domain - Select Security and Click on Credentials

The same will work in Oracle SOA Suite 12c but the screens will be little different.

• Click on Create Map

Enabling the HTTP Basic authentication to the Composite Service (Invoking a composite with HTTP authentication) – Oracle SOA Suite 11g

Enabling the HTTP Basic authentication to the Composite Service (Invoking a composite with HTTP authentication) – Oracle SOA Suite 11g

Sometimes we may need to enable the security like HTTP basic authentication to the composite service, so that the client can securely invoke our services providing the username/password.

This blog will explain the steps to enable HTTP basic authentication to our composite service. 

Configure the Authentication policy to the Composite Service:

• Open the composite.xml   

• Right click on the client service and click on Configure WS Polices

•  Add the security Policy oracle/wss_http_token_service_policy for authentication in the security section.