Angelos Italianknows Blog

Wednesday, 9 February 2011

SOASuite : Error Logging into BPM11g Composer?

Hey all, I’ve just installed SOA Suite and noticed a few funnies which people might hit, thankfully each of them have an easy solution.


1. Some applications are installed but dont appear to work?

If when you install SOASuite you may notice that the following applications dont appear to work, however they do appear as deployments in Weblogic Server Console

e.g.  SOA Composer (composer), FMW Welcome Page Application ( and some of the adaptors.

If they appear in the deployments list state as “installed” and not Active, then its likely that they haven't been targeted to a specific server.



The solution is to target the application the desired managed server , e.g. AdminServer in a development environment.

This is done by selecting the application, tab “Targets”, select all components, Button[change Targets] and select the appropriate server.

This change can be done without restarting the Weblogic Server

2. You might find that when you try to log into the BPM Composer at http://machine:7001/bpm/composer , the login screen will appear but you cant log in.

The error log might mention the following



The solution to this is two fold,

a) When creating the domain, avoid using as the Listener address, or “Any Addresses”, if this is a development machine create an alias in your /etc/hosts file and then use this alias in the domain creation wizard.

e.g.   my host file contains an entry    



And in the Fusion middleware Configuration wizard



Twill then work!


if it still doesnt you can try setting the ServerURL attribute to http://mypc in the SoaInfraMBean instead of blank.

This is accomplished by using Enterprise Manager. Use the System MBean Browser to navigate to Application Defined MBeans->>[ server]->SoaInfraConfig->soa-infra.

Then changing the value of 'ServerURL' to http://mypc


Failing that give support a call….

Weblogic 10.3.4 (PS3) nodemanager wont start?

Hi all, well Im back from Australia and one of the things which happened was Oracle announced the PS3 release of oracles SOA & Webcenter products have been released. Now I normally use pre-installed images but I always like to install the products at least once that way I get to see its installation caveats..

Here’s one.

Installation on Windows 7 64bit, 64bit JVM, generic weblogic Server installer.

All worked fine, EXCEPT I cant start the node manager, I get the following error

<08-Feb-2011 17:16:48> <INFO> <Loading domains file: D:\products\wls1034\WLSERV~1.3\common\NODEMA~1\>
<08-Feb-2011 17:16:48> <SEVERE> <Fatal error in node manager server>
weblogic.nodemanager.common.ConfigException: Native version is enabled but nodemanager native library could not be loaded
    at weblogic.nodemanager.server.NMServerConfig.initProcessControl(
    at weblogic.nodemanager.server.NMServerConfig.<init>(
    at weblogic.nodemanager.server.NMServer.init(
    at weblogic.nodemanager.server.NMServer.<init>(
    at weblogic.nodemanager.server.NMServer.main(
    at weblogic.NodeManager.main(
Caused by: java.lang.UnsatisfiedLinkError: D:\products\wls1034\wlserver_10.3\server\native\win\32\nodemanager.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(
    at java.lang.ClassLoader.loadLibrary(
    at java.lang.Runtime.loadLibrary0(
    at java.lang.System.loadLibrary(
    at weblogic.nodemanager.util.WindowsProcessControl.<init>(
    at weblogic.nodemanager.util.ProcessControlFactory.getProcessControl(
    at weblogic.nodemanager.server.NMServerConfig.initProcessControl(
    ... 5 more

Ok it appears that the node manager has gotten confused and thinks this is a 32bit install of Weblogic Server whereas it is the 64bit install.. Might have been something I did, or didnt do, on installation (e.g. –d64 on the jvm command line), however the workaround is pretty easy.


1. Create a file called in %WL_HOME%\common\nodemanager

on my machine it was D:\products\wls1034\wlserver_10.3\common\nodemanager

2. Add the following line to it


3. And start it up!, this will force it not to use .DLL files and use emulation/non native methods instead..