6 min read

Additional actions

In the following section, you will be performing additional configuration that is optional but will greatly improve performance and usability in the context of the development work you are about to start.

Setting memory limits

Review the memory settings. This value is dependent on your machine resources and may need to be adjusted for your machine. Allocating less memory for startup will give you better performance on a machine with less memory available. This value is appropriate for a 3 GB memory machine or less.

  1. Edit the SOA domain environment file found here (make sure you have the SOA Domain environment file):
    C:OracleMiddlewarehome_11gR1user_projectsdomains domain1
    binsetSOADomainEnv.cmd
  2. Set memory values:
    set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m

Starting and stopping

Now it’s time to start your servers. You can start them using the provided script or you can start them separately. Instructions for both methods are included.

Starting

First set boot.properties and then start the servers.

  1. Before you start, set the boot properties so you are not prompted to log in during server startup. Copy C:pobinboot.properties to C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1.
  2. Edit the copied file to reflect the password for your configuration (entered during domain configuration). The first time the server is started this file is encrypted and copied to the server locations.
    You can start the servers one at a time or you can use the start_all script to start the admin and SOA managed servers (not BAM). To start them one at a time instead, skip to step 6.
  3. Copy the startup script to the Oracle directory:
    C:pobinstart_all.cmd to
    C:OracleMiddleware
  4. Edit the copied file to reflect your environment.
  5. Open a command window and start your servers as shown. You must specify how many seconds to wait after starting the admin server before starting the managed server. The admin server must be in the RUNNING state before the managed server starts (see the following screenshot). Try 180 seconds and adjust as necessary. You will need more time the first time you start after a machine reboot than for subsequent restarts:
    cd C:OracleMiddleware
    start_all.cmd 180

    Your servers are now starting automatically so you can skip steps 6-10. Jump to step 12 to continue.

    To start the servers manually, continue with the following steps.

  6. Open three command windows, one for the WebLogic admin server, one for the SOA managed server, and one for the BAM managed server (only start BAM when you need it for a BAM lab).
  7. Start the Admin Server first:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    startWebLogic.cmd
  8. Wait for the Admin Server to finish starting up. It takes a few minutes—watch for status RUNNING in the log console window:

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  9. Start the SOA managed server in the second command window. This start script is in the bin directory. You can also run it directly from the bin directory:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    binstartManagedWebLogic.cmd soa_server1
  10. When prompted, enter the username weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. The server is started when you see the message, INFO: FabricProviderServlet.stateChanged SOA Platform is running and accepting requests.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  11. Start the BAM managed server in the third command window—do this only when needed for the BAM lab:
    cd C:OracleMiddlewarehome_11gR1user_projectsdomainsdomain1
    binstartManagedWebLogic.cmd bam_server1
  12. When prompted, enter the user name weblogic and password welcome1. If you did step 1 and set boot.properties, you will not be prompted. Watch for the RUNNING status.

Console URLs

Log in with weblogic/welcome1 for all consoles:

  • Weblogic console: http://localhost:7001/console
  • Enterprise Manager console: http://localhost:7001/em
  • SOA worklist: http://localhost:8001/integration/worklistapp
  • B2B console: http://localhost:8001/b2b
  • BAM (must use IE browser): http://localhost:9001/OracleBAM

Stopping servers

Whenever you need to stop the servers complete the following:

  1. Stop the managed servers first by entering Ctrl+C in the command window. Wait until stopped.
  2. Stop the admin server by entering Ctrl+C in the command window.

WebLogic Server console settings

There are two suggested changes to make in the WebLogic Server console.

First, you will be viewing application deployments often using the WebLogic server console. This is a lot more convenient if you change the settings not to show libraries as this makes the list a lot shorter and you can find what you need more quickly.

  1. Start the WebLogic Admin Server (WLS) if it is not already running.
  2. Log in to the WLS console http://localhost:7001/console.
  3. Click on Deployments in the left navigation bar.
  4. Click on Customize this table at the top of the Deployments table.
  5. Change the number of rows per page to 100 (there are only about 30).
  6. Select the checkbox to exclude libraries and click on Apply.

Second, when the server is started, internal applications like the WLS console are not deployed completely and you see a slight delay when you first access the console. You saw this delay just now when you first accessed the console URL. You can change this behavior to deploy internal applications at startup instead and then you don’t get the delay when you access the console. This is convenient for demos (if you want to show the console) and also if you tend to use the console each time you start up the server.

  1. Click on domain1 in the left navigation bar in the WLS console.
  2. Click on Configuration | General tab.
  3. Deselect Enable on-demand deployment of internal applications checkbox.
  4. Click on the Save button.

EM settings for development

The Enterprise Manager can provide different levels of information about composite runtime instances based on a property setting. During development, it is helpful to have a higher setting. These settings are not used on production machines except when specifically needed for debugging purposes as there is a performance cost.

  1. Start your servers if they are not already running.
  2. Log in to the EM console at http://localhost:7001/em.
  3. Right-click on the soa-infra (soa_server1) in the left navigation bar to open the SOA menu and select SOA Administration | Common Properties.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  4. Select Audit Level: Development and select the checkbox for Capture Composite Instance State.

    Installation and Configuration of Oracle SOA Suite 11g R1: Part 2

  5. Click on Apply and click on Yes.

If you need to uninstall JDeveloper and servers

If you need to uninstall everything, complete the following:

  1. First save anything from C:OracleMiddlewarejdev_11gR1jdevelopermywork that you want to keep as this directory will be deleted.
  2. Run Uninstall from the program menu to completion for both JDeveloper and WLS.
  3. Delete C:OracleMiddlewarejdev_11gR1 and C:OracleMiddlewarehome_11gR1. If you get an error message about not being able to delete because a name or path is too long, change the names of the composite directories within home_ 11gR1user_projectsdomainsdomain1deployed-composites to abcd and try deleting again.
  4. Delete program groups from C:Documents and SettingsAll UsersStart MenuPrograms:
    • Oracle Fusion Middleware 11.1.1.1.0
    • Oracle SOA 11g – Home1
    • Oracle WebLogic
  5. Complete the Dropping existing schema section earlier in this article to clean up the database.

Subscribe to the weekly Packt Hub newsletter. We'll send you this year's Skill Up Developer Skills Report.

* indicates required

LEAVE A REPLY

Please enter your comment!
Please enter your name here