Configure SOA 10.1.3.4 with weblogic 9.2

The best option is to check the following Metalink note 753899.1

You can have the installation guide by downloading patch 7490612

ONce you download the patch extract it

and you can locate the installation guide in following location

Weblogic_SOA10134\InstallandUpgradeDoc\E13058_01.pdf

All the steps has been clearly mentioned in this note.I am just providing the screenshots if in any case you might find problem at some stage you can have a look at the same.


For platforms where WebLogic Server does not include a JDK, install the latest version of JDK 5.0 installation for the appropriate platform.

NOTE: When any of the subsequent installation/configuration steps ask for the JAVA_HOME, make sure to point to the directory where you have installed this new version of the JDK 5.0 or the JDK 5.0 version that comes with WebLogic Server


Screenhots for installation
===============================
I am doing advance installtion of SOA Suite so i believe you already have the database installed. I have 10.2.0.3 database at my end to which i will point out while installing soa suite for dehydration store.YOu should have the schemas already created at database using irca.bat file.I will go ahead with installation of SOA Suite.

Istall SOA Suite 10.1.3.1

Start the installation wizard.

setup.exe.YOu will get the following screen .Choose the first option.Go for advacned installation.





The next window will ask for the database details.I am using advanced insatlltion of SOA Suite so i am using 10.2.0.3 database as my dehydration store.So specify the details of database



Moving ahead the istallation wizard will ask for the password for three different schemas.These schemas are orabpel,oraesb and orawsm.These act as a dehydration store.I am using the same password for all the schemas.



Now if you want to configure port you have to set it to manual and have to point to the staticports.ini.However i am using the default automatic value.




Moving ahead it will ask for administrator settings.

provide those details




Next is cluster topology settings.We will configure it later.For the time being just say next




Moving ahead it will come up with the installation page.It will show all the components that are being installed.Please check whether you fulfill the space requirement or not.





Say install and it will start installing the components




The next window will show whether the different components have been insatlled successfully or not.




Finally it will come up with end of installation.



Once you will say exit the admin console will open up automatically.


ONce installed successfully.Please try to login in to BPEL console

Http://localhost:port/BPELConsole

with user oc4jadmin and your password.

Also try to login in to esb and rule author console.

Everything is working fine.

So now we will upgrade our 10.1.3.1 to 10.1.3.4

Upgradation of SOA Suite 10.1.3.1 to 10.1.3.4
=================================================
While upgrading SOA Suite 10.1.3.1 the database and listener should be up and running and the SOA Suite should be down.

I am not running any schema upgrade now as mentioned in the readme of the patch.I will apply the upgradation script after installation of patch set.

You can do the same from command console

Go to following location in command console

SOA_HOME/opmn

and say opmnctl stopall


Extract the patch set and run the setup.exe

Provide the name for the destination and point the destination path to the SOA Suite home where in you have installed SOA Suite.



Provide the administrator password.For avoiding confusion i give same password for everything.



It will comeup with the summary screen



Go ahead and say install.Installation wizard will start and will come up with a screen like this.




Configuration assistance will now show whether installation of each component are successfull or not.




Finally end of isntallation will come up and you have to say exit.



Upgrade the schema by running the scripts mentioned in the readme.

Restart your SOA Suite and check all the console.

So far we have done the installtion of SOA Suite 10.1.3.4

Now we will go ahead for weblogic installation.


As per note the next step is

Install the Opatch version 10.1.0.0.0 with the patch number 6880880.
========================================================================

In order to install the opatch you need to download this patch 6880880.Once downloaded extract the patch .YOu will get a folder with name Opatch.

YOu only have to replace the OPatch in SOA_HOME with this opatch.Take the backup of previous OPatch folder and replace it with the new opatch downloaded.


Install patch number 7337034
===============================
Download patch

and in command console move up to 7337034

Set ORACLE_HOME and PATH

and say opatch apply.




After some time it will ask if the system is ready for updating .Say Y as shown below



Finally it will come up as opatch succedded
Opatch returned with error code 0




At present the SOA Suite 10.1.3.4 is certified with Weblogic 9.2.
The same is mentioned in oracle forum link

http://forums.oracle.com/forums/thread.jspa?threadID=696888

So now we will go ahead and install weblogic9.2

Installtion of weblogic9.2
=============================

Installing weblogic is very easy and you just have to run the installation wizard and give the location where you want to have your weblogic installed.So i believe the screenshots will be just enough.








Go for complete installation




Just keep on selecting the default values.










Istallation done for weblogic9.2

This installtion will come up with a default domain and an example admin server. I believe if you are installing weblogic you are aware of domains and servers concept.I will explain it may be later.For now i am only giving screenshots so as to make it easy for you to understand.The default user name and password for weblogic admin console is weblogic only.

Now the next step is to Apply patch 7490612
=============================================

This patch creates a new domain and a server.YOu can point it to the default domain created with weblogic installation,However i choose to create a new domain.

Each domain has a admin server and can have many managed server.Well leave the concepts go for installation.You can do lot of R&D after it got installed successfully.

Download and extract the patch.

Therafter go to following location

Weblogic_SOA10134\Weblogic_SOA10134_Base and open SOADomain.properties file.

There enter the path separators as "\\", not "\" for windows.

If you are using "\" you might get an error

UnknownElement : Task "property" finished with error.
java.lang.IllegalArgumentException: Malformed \uxxxx encoding.


Now move up to Weblogic_SOA10134\Weblogic_SOA10134_Base in command console and execute setup.bat.

One important thing to keep in mind is we have jrockit and jdk.If you are on developement mode it is suggested to use normal jdk and if you are in production mode you should use jrockit.I am using it is developement mode so i will choose jdk.I will use the default jdk provided with the weblogic installation.

So provide the path for jdk in the SOADomain.properties

Once you will run setup.bat it will ask for three details

JAVA_HOME,BEA_HOME and WL_HOME

You need to provide the same value as you have provided in the SOADomain.properties.



It will create a new admin server and managed server in the new domain you choose to create.It will ask for password.provide password.



Finally it will come up with build successful.



Now start the webloging server from the new domain and try to login to admin console

You can check the port number and ip location from console where you have to connect.

You need to set the domain first by using setDomainEnv.cmd then run startWebLogic.cmd

Start node manager from console.

It will be within the default domain created under bin

\server\bin

Now start the node manager from the admin console.

The SOA Suite should be in a shut doen state.

Once Maanged SErver is started Go to deployments and check if all the components are active or not.

NOw as per note try to log in to the bpel console

http://localhost:9700/BPELConsole

You might get an error like this

The console page will take more than expected time to come up and will display an error

Oracle BPEL Process Manager Full Cycle
An unexpected error has occurred while executing your request. This is most likely related to a defect in the Oracle BPEL Process Manager product. We apologize you can post the error to the OTN forum and we will get back to you as soon as possible.
Build Information:
*****************************************************************************
Oracle BPEL Server version 10.1.3.4.0
Build: 0
Build time:
Build type: release
Source tag: PCBPEL_10.1.3.4.0_GENERIC_080718.0645
Exception Message:
java.lang.OutOfMemoryError - Java heap space


NOw if you will check the console which you have used to start the admin console for new domain created .You can find the values for Xms and Xmx as

JAVA Memory arguments: -Xms256m -Xmx512m

You can also check the same from setDomainEnv.cmd file ,YOu will get it under MEM_ARGS

Now you have to change it according to your available physical RAM.

If you have a Physical RAM of 4GB you can make these parameter as -Xms1024m -Xmx1024m

It is recommended to make both these values same for better performance.

What it will do is it will take 1 gb of RAM each for admin server and managed server.
That is now you are left with only 2gb of free RAM.So depending upon the other applications being used you can set these parameters.


Make these changes and restart the weblogic server.You will be able to log in to bpel console.
=====================================


It can also happen that your new domain server will shut down automatically giving this error in console



and giving following error in the browser




This is because your log files are constantly increasing

if you will go to the new domain created and check the files

\servers\managedSErverName\logs

ManagedSErverName.out is constantly increasing and increasing.

Remove all the log files

Now go to server console

Go to logging

Go to advacned setting

Change the severity level to info

For Domain log broadcaster : Severity level:Make it as error

Restart the server.

You will be able to see now everything.
==============================================

So now you have installed weblogic with SOA Suite so go ahead and create a connection with jdeveloper and start deploying process.


While trying to create a connection to weblogic with jdeveloper it may give error.

Cannot instantiate class: weblogic.jndi.WLInitialContextFactory

The following forum link gives the solution for the same

http://forums.oracle.com/forums/thread.jspa?threadID=825796

Copy the \server\lib\weblogic.jar to the \jdev\lib\ext directory.

Restart the jdeveloper and you will now be able to create a connection.
=============================================================================
If you are getting following error while opening the console for BPEL/esb/workflow


Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.


Check out in deployments if all the applicaton deployed are active or not.If they are not active choose the application and start it.Even if it doesn't start then

1>shutdown your managed server.
2>Shutdown admin server.
3>Start nodeManager from command console
The command can be found in weblogic92/server/bin directory
4>Start admin server
The command can be found in weblogic92/server/bin directory
5>Then log in to admin console and start managed server from admin console.

Now all the deployment should be in active state.


As soon as you will find every thing is working fine at your end(try deploying a bpel process and check if it deploys successfully and appears in bpel console),I would recommend to go ahead and apply patch 7586063 which is MLR#3 on top of SOA Suite.It is because MLR#3 resolves a lot of issue for example-in base soa suite 10.1.3.4 with weblogic 9.2 the weblogic is not able to recover from lost jdbc connection.That is if you will shutdown the datasource and then resume still the log file OracleSOAServer.out will keep on increasing in size and will stop only if you will restart the server.

YOu might receive this kind of error

SEVERE: Failed to process deferred message
oracle.tip.esb.server.dispatch.QueueHandlerException: Subscriber not exist for system "0_BPELSystem"

at oracle.tip.esb.server.dispatch.JMSDequeuer.dequeue(JMSDequeuer.java:168)
at oracle.tip.esb.server.dispatch.agent.ESBWork.process(ESBWork.java:174)
at oracle.tip.esb.server.dispatch.agent.ESBWork.run(ESBWork.java:132)
at weblogic.connector.security.layer.WorkImpl.runIt(WorkImpl.java:108)
at weblogic.connector.security.layer.WorkImpl.run(WorkImpl.java:44)
at weblogic.connector.work.WorkRequest.run(WorkRequest.java:93)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

so to avoid this better update your SOA Suite to MLR#3