Finally good news that SOA Suite 10.1.3.5.1 is available which:
- Runs on Weblogic 10.3.1
- Full install so no need to go base install and then patch and then MLR, one install has it all
Essentially its a
- Install Weblogic
- Create schema using IRCA (not GUI based yet, so still the same command line interface of 10g)
- Install SOA Suite
- Configure SOA Suite and then
- Post configuration steps.
Process is smoother and looks less prone to errors.
Step 1: Weblogic Server Installation
Click on setup
- On welcome screen, click Next
- Create new BEA home and click next.
- For some reason, my id didn’t work so choose to skip this step and click next
- Choose “custom” option as we don’t want to install eclipse as well as server examples
- Select JRockit as the JVM. Although it will install both and we can switch to Sun JVM after install.
- Provide weblogic’s installation directory. Please remember that SOA Suite (Step 2 of installation) needs to be at same folder level.
- Choose to skip node agent service.
- Select “All Users” and click next
- View summary and click next
- Installation summary
- Uncheck “Run Quickstart” and click done. We will run comfit wizard after step 2 (SOA suite installation).
Step 2: SOA Suite 10.1.3.5.1 installation
- Create schemas for BPEL/ESB/OWSM using IRCA
- Click on setup, on welcome screen click next.
- select your ORACLE_HOME, remember that Weblogic Server and SOA Suite should be installed at same folder level.
- Choose Language and click next
- Specify weblogic server installation directory and click Next.
- I didn’t require a proxy configuration so skipped it
- Specify dehydration store details
- View summary and click install
- Installation progress screen
- Configuration assistant screen, remember this is not the same as we have in OC4J version. Here it performs just one task whereas in OC4J version it does all the comfit (BPEL/ESB/OWSM etc).
- View installation report and click Exit.
Step 3: SOA Configuration
- Start SOA configuration assistant, this will prompt you for ORAWSM password. There is a way to do it silently, but I tried it in interactive fashion.
- After initial script, configuration wizard is kicked off. Here we will create a domain with 2 servers (1 admin + 1 SOA). I am in process of working of creating both on 1 server (only for developer’s machine). Select for creating a new domain and click next
- Select “SOA Suite” as part of this configuration and click next
- Specify domain name and click next
- Specify domain user name and password. By default username if “weblogic” but i prefer fmwadmin now. Remember the password as this will be the same password for “soaadmin” user which will be automatically created as part of configuration script. This user will allow you to access bpel/esb/owsm consoles.
- Select startup mode (i selected development) and JDK which I choose to use JRockit.
- Configure BPEL and ESB db connection parameter (remember OWSM is already done at the beginning of configuration).
- Test your connection settings and click next
- Select all the checkboxes and click next
- Specify admin server name and port. I didn’t enabled SSL but we can do it later after install as well.
- Give managed server name and port. I left it to default values. Again no SSL but if required we can do it from weblogic admin console after this setup.
- Developer’s machine so no need to setup this
- Configure machine and node manager
- Move managed server under the machine created earlier.
- Select managed server and select all the applications under deployment. Do not select any deployment for admin server.
- Check JDBC and JMS resources
- Configure JMS file store, i kept default values, however you want to specify different directory feel free to do so.
- No security configuration required, so left it at default
- View the configuration summary screen and click create
- Once finished click done and close the window.
Step 3: Post Configuration Steps.
- Change topic location for ESB Systems to “ESB_JAVA_DEFERRED” also update host and port. You can ignore value of connection factory location as its not pertinent because of AQ JMS APIs
- Set StartScriptEnabled=true in nodemanager.properties if you want to use start/stop managed servers from console. I prefer to not to run nodemanager because of resource reason, so to avoid providing userid password for starting managed server, i modified startManagedWeblogic.cmd and update WLS_USER and WLS_PW and SERVER_NAME parameters like
set WLS_USER=fmwadmin
set WLS_PW=welcome1
set SERVER_NAME=soa10g_server1
- Download the velocity-dep-1.5.jar file from http://archive.apache.org/dist/velocity/engine/1.5 and copy it under bpel\lib directory. This would enable “notification” feature which is new to 10.1.3.5. Notification feature allow you to monitor system events like deploy, undeploy, retire, on/off of process and send emails etc.
- Restart servers and check all the applications using “soaadmin” user
- Console (/console)
- BPELConsole (/BPELConsole)
- ESB (/esb)
- OWSM (/ccore)
- Worklist application (/integration/worklistapp/
