Oracle BPM 12C - BPM workspace timed out error

I was using Oracle BPM 12.1.3 version and getting BPM workspace  timed out very often after submitting the task.  I also gone through BPM workspace and application configuration but everything looks normal.

BPM Workspace configuration

console->deployment->OracleBpmWorkspace->/bpm/workspace->configuration
Session Timeout =1000
Session Invalidation= 60


Application Configuration

CustomerPortal->/workflow/ViewController(war)->Configuration
Session Timeout=4000
Session Invalidation= 90

Solution:

 

I gone through some of the oracle documentations and found out we can set INVALIDATE_SESSION_ON_LAST_RVP_RELEASE parameter can be set as FALSE in adf-config.xml file to get rid of this error.

<adf-controller-config xmlns="http://xmlns.oracle.com/adf/controller/config">
<adf-scope-ha-support>true</adf-scope-ha-support>
<invalidate-session-on-last-rvp-release>false</invalidate-session-on-last-rvp-release>
</adf-controller-config>

 After this setting timeout error was gone.

OSB 12C - Not able to login to SB console - Error 401--Unauthorized

When I was trying to login into OSB console http://localhost:7001/servicebus/, I  got Error 401--Unauthorized error on the browser. It was happening on OSB 12.1.3.0.0 version.

ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.[[
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: User 'weblogic' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.

Reason:

After some investigation and following oracle documentation , i found out that i was using JDK 1.8 which was not certified with Oracle SOA Suite 12C 12.1.3.

Solution:

Download  and install  JDK 1.7 from  oracle site and reconfigure the weblogic start and managed scripts within and <wls_domainHome/bin> to update the JAVA_HOME parameter to your new JDK 1.7 install.

Restart the admin and managed servers. Now you wouldn't see that issue again.

OSB 12C : The conversion of MFL to XSD fails in an OSB 12c project

When using the Native Format Builder wizard in JDeveloper for an OSB project, the conversion from MFL to XSD fails with the error 'Root element must be provided.'.

Solution

Please use a SOA project for the conversion from MFL to XSD instead of an OSB project.

The feature is for SOA and is not for OSB in current JDeveloper. The feature for OSB has been requested as an enhancement.

Oracle SOA 12c : SOA 12c XSLT processor fails with an empty function definition

When invoking a function whose definition is empty (i.e. is syntactically valid but does not contain any transformation nodes), the 12c SOA Suite engine (and JDeveloper 12c) fail during execution and return an error message.

Error message in 12c: Failed to transform source XML. oracle.xml.xpath.XPathException: EmptyFunction function under namespace internal is not defined

It was working in 11g version it worked and it fails in 12c version.

Solution:

Oracle support has provided a patch to fix this issue.

Apply <Patch 21571604>

To implement the solution, please execute the following steps:

1. Download and review the readme and pre-requisites for the Patch
2. Ensure that you have taken a backup of your system before applying the recommended patch.
3. Apply the patch in a test environment.

4. Confirm that the above interim patch has been successfully applied by executing the following command:

opatch lsinventory -detail.

5. Retest the issue.
6. Migrate the solution as appropriate to other environments.

OSB 12C :WSM-06404 error in a WS-AT web service call on OSB 12c

When executing a WS-AT web service operation the following error is thrown:

<WSM-06404> <The resource pattern "ResourcePattern [absolutePortableExpression=/WLS/osbdomain/|#MODULE|WS-Client({http://schemas.xmlsoap.org/ws/2004/10/wsat}WSAT10Service#ParticipantPortTypePort,wls)]" does not uniquely identify the subject.>

It was caused due to transaction is being left open even after the message was consumed.

Solution:

Use @TransactionManagement(value=TransactionManagementType.CONTAINER) instead of @TransactionManagement(value=TransactionManagementType.BEAN) in the web service.

Oracle SOA 12c OWSM :validation errors: WSM-02557' during SOA server startup after upgrade to 12c

I got following exception while starting SOA server after 12C upgrade

<oracle.j2ee.ws.rm.WSRMLogMessages> <WSRMLogMessages> <logWarningUnexpectedError> <OWS-25106>

javax.xml.ws.WebServiceException: WSM-02557:oracle.wsm.policymanager.accessor.BeanAccessor:The documents required to configure the Oracle Web Services Manager runtime have not been retrieved from the Policy Manager application (wsm-pm), possibly because the application is not running or has not been deployed in the environment. The query "&(@appliesTo~="WS-CLIENT()")(policysets:global/%)" is queued for later retrieval..

               at oracle.j2ee.ws.common.wsm.WSMPolicyHelper.retrievePolicySet(WSMPolicyHelper.java:736)

               at oracle.j2ee.ws.client.jaxws.DispatchImpl$1.run(DispatchImpl.java:600)

               at oracle.j2ee.ws.client.jaxws.DispatchImpl$1.run(DispatchImpl.java:594)

               at java.security.AccessController.doPrivileged(Native Method)

               at oracle.j2ee.ws.client.jaxws.DispatchImpl.getPolicySet(DispatchImpl.java:594)

               at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.getPolicySet(OracleDispatchImpl.java:180)

               at oracle.j2ee.ws.rm.util.RMUtils.getInterceptorConfigForDispatch(RMUtils.java:513)

               at oracle.j2ee.ws.rm.util.RMUtils.getClientConfigurationInfo(RMUtils.java:144)

               at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

...

oracle.wsm.policy.advertisement.AdvertisementException: WSM-01709 : The Runtime PolicySet cannot be advertised due to validation errors.

Solution :

1. Log into the WebLogic Console, click on deployments, and validate that owsm-pm is targeted.Log into EM (Fusion Middleware Control), right click on the WebLogic domain/<domain>.

2. In the domain dropdown, select cross component wiring/components.

Select OWSM Policy Manager

Make sure the OWSMPM entries are not out of sync and make sure the URL is correct. This is the advertised location of the wsmpm application in the domain.

If it is out of sync, hit publish.

Select OWSM Client

Make sure owsm pm entries are “wired” and make sure the URL is correct. This is the configuration of the client on where to find the owsmpm application.

 If out of sync, click Bind and verify that the new address is correct.

Restart all the servers.

Oracle B2B :Unable To Access Oracle B2B 12c Console

After installation when I was trying to access b2bconsole, I got following error

ERROR
-----------------------
[2015-09-03T09:42:59.309-04:00] [soa_server1] [ERROR] [] [org.apache.myfaces.trinidad.webapp.UIXComponentELTag] [tid: [ACTIVE].ExecuteThread: '12' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 9c892099-a6a3-49b1-90ee-d4c5a34cbedc-000ad130,0] [APP: b2bui] [DSID: 0000KyJSWXnESO15zvc9yW1LpQ19000003] Error when processing tag for component with id: "selectedPolicyTable". The scoped id of the parent component is ":tpProfilePanelPage:selectPolicyHeader".[[
javax.faces.FacesException: com.sun.faces.mgbean.ManagedBeanCreationException: Cant instantiate class: oracle.tip.b2b.ui.backing.partner.TpChannel.
at com.sun.faces.application.ApplicationImpl.createComponentApplyAnnotations(ApplicationImpl.java:1952)
at com.sun.faces.application.ApplicationImpl.createComponent(ApplicationImpl.java:447)
at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:222)

The main reason for this error was i have not extended the domain for B2B

Solution :

Extend the domain to include b2b as indicated in Chapter "17 Extending the Domain with Oracle B2B" of the Enterprise Deployment Guide.

Restarted all the servers. I was able to access the B2B console.