Launching and Testing the SOA Suite11g Weblogic Servers

Launching and Testing the SOA Suite 11g WebLogic Servers:

• Start the Admin server – use the command [MIDDLEWARE_HOME]/user_projects/domains/SOA11g/startWebLogic.cmd
• Start the managed server, soa_server1 – use the command [MIDDLEWARE_HOME]/user_projects/domains/SOA11g/bin/startManagedWebLogic.cmd soa_server1
• There is no need to start the BAM server at this point but if you did, you would use the command [MIDDLEWARE_HOME]/user_projects/domains/SOA11g/bin/startManagedWebLogic.cmd bam_server1
• If you’re starting the integrated Admin and SOA server domain, you would use the command

[MIDDLEWARE_HOME]/user_projects/domains/SOA11g_Admin_And_SOA_Servers/startWebLogic.cmd

You’ll know the domain is ready when the line “SOA Platform is running and accepting requests” message appears in the console:

Managing Memory:

Most developers these days have 4GB RAM available on their desktops while some are still using 2GB.  Starting up 3 weblogic server instances on a single development desktop can have an expensive memory footprint as each WebLogic server instance can take up on the average of 750MB of RAM.  For this reason, it is typical to have an integration test environment up and running on a separate machine from the developer desktop where JDeveloper is used.  It is also typical to have a database server separate from the SOA Server, once again to ensure that there is a large enough memory pool available for the application servers and that the database server doesn’t starve the mid-tier.

Many companies are now starting to use large memory servers and then split those resources up among virtual machines for development and QA environments.

The SOA composites are then deployed to the remote SOA Server instances so that the developer desktop can still function smoothly with a typical memory footprint.

Testing the New SOA Domain:

First, ensure that the Enterprise Manager (EM) console works.

Go to the URL: http://localhost:7001/em

You will be prompted to login with the administrator user/password which is “weblogic/welcome1”

After login for the first time, you will be given the option for using a screen reader for accessibility.  If this isn’t needed, select “Do not show me these options again” and hit the “Continue” button.  At this point, you will see the overview view of enterprise manager.

Expand “SOA” in the left-hand navigation tree and select “soa-infra” to see the dashboard for the SOA runtime infrastructure.  For the first time you will see that no composites have been deployed.  During development, this is where you will spend time testing the SOA composites.  Note the other infrastructure components that can be viewed and managed through EM including: applications, resource adapters, the WebLogic domain, Metadata Repositories, and User Messaging Services.

Next, check to make sure that the WebLogic console works.

Go to the URL: http://localhost:7001/console -