Hey all, I’ve just installed SOA Suite 11.1.1.4 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 (11.1.0.0.0) 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 127.0.0.1 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
mypc 127.0.0.1
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->oracle.as.soainfra.config->[ server]->SoaInfraConfig->soa-infra.
Then changing the value of 'ServerURL' to http://mypc
Failing that give support a call….
ort/em ) , however we were thinking this isnt a “user friendly” way of doing this.. 