Weblogic Server provides runtime MBeans which provide information about the runtime state of its resources. The entry point for these MBeans are the MBeanServer Services. There are two Runtime MBeans, the DomainRuntimeServiceMBean, which is only available at the Administration Server and the RuntimeServiceMBean which is the entry point for WLS runtime MBeans for the current server. WLS runtime MBeans can provide information about the runtime state of WebLogic Server resources. An overview of the available Runtime MBeans can be found in the Weblogic Server MBean Reference. Sometimes it can be useful to retrieve data from these Runtime MBeans in a BPEL process. For example the name of the Weblogic domain, the machine or the managed server whereon the BPEL process is running.

Here is an example how you can retrieve the Weblogic Domain Name, Machine Name and Server Name whereon the BPEL instance is running.

Tweet
Read More...

Just a quick post about an issue i ran in today which maybe can helpful. Today the migration of a specific Oracle 10G esb service failed using our ant SCA-build script. In the ant script a task, upgradeESB, is defined based on the class oracle.ias.upgrade.task.MediatorUpgradeTask. During the execution of the upgradeESB task the portType in the wsdl of the esb service is fetched (UPGMED-02044). Although the portType is there, it is not found (UPGMED-02045) in the wsdl and subsequently also not in the service resulting in a MediatorUpgradeException, UPGMED-02047.

Tweet


Read More...

Although my SOA Suite composites deployed without any error, for some of them JDeveloper returned a “Error while reading wsdl file …. Exception: null” error when opening one of my external references to adapters within that composite. This general occurred to me after upgrading a 10g BPEL service to a 11g composite. When receiving this error, a namespace or attribute within the adapters WSDL can be incorrect, but i also found out that it can show up when the WSDL is 100% correct. This is probably due to a bug in JDeveloper Studio Edition Version 11.1.1.5.0 or 11.1.1.6.0. Here some hints where to look for in the WSDL, how to solve the issue and eventually working around the JDeveloper bug.

Tweet
Read More...

In the process of upgrading 10G BPEL proces to 11G composites we encountered "Content is not allowed in prolog. ORABPEL-01501" and "XML-20109: (Fatal Error) PI with the name 'xml' can occur only in the beginning of the document." errors. Major cause is that the original BPEL processes do contain schemas delivered by external organizations in a variety of encodings. Some of them did contain within the encoding not allowed characters which were accepted in 10g but do not pass the more strict validation of schemas in 11g. To forestall most of these issues i wrote the folioing ANT target which is called during the upgrade process to correct most (not all!) of these file encoding issues.

Tweet
Read More...

Because Oracle BPEL 10G does not have a as strong validation of BPEL processes as in Oracle 11G it is possible that 10G services which appeared in 10g syntactically correct fail to compile after migrating to 11G. One error which can occur is 'Error: Load of wsdl "{WSDL_A} with Message part element undefined in wsdl [{WSDL_B}] part name = parameters type = …" failed'.

The error is caused by a conflicting namespace in one of the imported WSDL or Schema files. This can be a WSDL or Schema directly imported in the composite.xml or a WSDL or Schema imported by another WSDL. The error is misleading, the root cause of the error will with any certainty not be in the reported file WSDL_A. When having more complex BPEL services with multiple partnerlinks it can be challenging to find the namespace conflict. Here a structured way to get to the source of the problem.

Tweet Read More...

Tags: Load of wsdl failed, 11G Migration, SOA Suite, BPEL