Is your server ready for FP Installation?
By Raghavateja on Jul 12, 2009
I notice quite a few times that FP installation fails because of issues with SOA suite and DB and I hear queries on how to make sure SOA Suite is ready for Foundation Pack installation.
Make sure your answer is ‘YES’ to all of the below questions. This might not be an exhaustive list of pre-requisites, but will certainly eliminate most of the common errors.
1. Are you using the right version of JDK?.
Each version of Foundation pack is certified with a different version of JDK. Verify the installation guide and metalink notes to check for the most recent version. The last version of Foundation pack was certified on JDK 1.5 update 16
2. Does the DB user have DBA privileges?
The DB user entered during interview screens should have privileges to create a db schema. ‘sys’ user usually has all the required privileges.
3. Is directory browsing enabled on the server?
Check the install guide for information on how to enable directory browsing on your server.
4. Is your ESB working properly?
a. Ensure ESB design time and runtime are accessing the following urls.
both the pages should return a true.
b. Deploy a sample ESB process from ESB Console and execute it to check the results.
c. Create a sample ‘system’ from ESB Console.
d. Ensure virtual host and port of BPELSystem and DefaultSystem are set appropriately in ESBConsole.
5. Is your BPEL PM working properly?
a. Deploy a sample BPEL process and verify the flow eg: LoanFlow demo.
b. Verify if you are able to login to BPELConsole and navigate across various pages
Note: remember to undeploy the samples and delete the previously created system.
6. Verify that you don’t have any existing applications in your SOA cluster starting with “default_”.
For example if you had deploy the LoanFlow demo, it would’ve created such applications.
To check this
i. Open the EM Console
ii. Navigate to the container
iii. In the Applications tab, drill down from BPEL>orabpel.
iv. Select any application starting with “default_” and undeploy