Task 2: Install the Fusion Order Demo Application

3-4 Oracle Fusion Middleware Developers Guide for Oracle SOA Suite

3.2.3 Task 3: Install Oracle SOA Suite

To successfully deploy and run the Fusion Order Demo applications, you must complete an installation for Oracle SOA Suite. Specifically, the domain contains an Administration Server and a Managed Server. Installing Oracle SOA Suite requires the following ■ Creating schemas for Oracle SOA Suite in an Oracle database ■ Installing Oracle WebLogic Server ■ Configuring a domain in Oracle WebLogic Server to support Oracle SOA Suite, Oracle Enterprise Manager, and optionally, Oracle BAM. Oracle BAM is not required for the Fusion Order Demo, but if an Oracle BAM Server is configured, Oracle BAM adapters send data to the Oracle BAM Server. After the domain is created, it contains an Administration Server to host Oracle Enterprise Manager Fusion Middleware Control for performing administrative tasks, a Managed Server to host deployed applications, and, if you configured Oracle BAM, a second Managed Server for the Oracle BAM Server. For instructions on installing and configuring Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite. After successfully completing the installation process, perform the following additional configuration steps: 1. Enable the credentials that are included in the StoreFront module by adding a setting to the configuration file for the domain: a. Locate the configuration file set for the Oracle SOA Suite domain in the following directory: UNIX MW_HOMEuser_projectsdomainsdomain_namebinsetDomainEnv.sh Windows MW_HOME\user_projects\domains\domain_name\bin\setDomainEnv.cmd b. Add the following option to the JAVA_PROPERTIES UNIX or the SET JAVA_PROPERTIES Windows line: -Djps.app.credential.overwrite.allowed=true For more information about setting this property, see Oracle Fusion Middleware Fusion Developers Guide for Oracle Application Development Framework. c. If the Oracle WebLogic Server Administration Server is running, stop it: On UNIX, as the root user, change directories to directory MW_HOMEuser_ projectsdomainsdomain_namebin and enter the following command: .stopWebLogic.sh On Windows, from the Windows Start menu, select All Programs Oracle WebLogic User Projects domain_name Stop Admin Server. d. Start the Administration Server: On UNIX, from directory MW_HOMEuser_projectsdomainsdomain_ name bin, enter the following command: .startWebLogic.sh On Windows, from the Windows Start menu, select All Programs Oracle WebLogic User Projects domain_name Start Admin Server. Introduction to the SOA Sample Application 3-5 When prompted on UNIX, enter your Oracle WebLogic Server user name and password. The password is not visible as you type. The Administration Server is started when the command window displays the following messages: Server state changed to RUNNING Server started in RUNNING mode Leave the command window open, although you may minimize it. The Administration Server is now running and ready for use. e. When the Administration Server is in RUNNING mode, start the Managed Servers, if they are not running. In a command window, enter the following command all on one line: On UNIX, from directory MW_HOMEuser_projectsdomainsdomain_ name bin, enter the following command: .startManagedWebLogic.sh managed_server_name admin_url username password On Windows, from directory MW_HOME\user_ projects\domains\domain_name\bin, enter the following command: startManagedWebLogic.cmd managed_server_name admin_url username password Substitute the following values in Table 3–1 .

2. If you are deploying remotely from one computer that has Oracle JDeveloper to

another computer that has the Oracle SOA Suite installation with Oracle WebLogic Server, modify the JAVA_HOME and PATH environment variables on the computer with the Oracle SOA Suite installation. Oracle JDeveloper requires changes to these variables for running the scripts that deploy the composite services. You set the JAVA_HOME variable to include the path to the Oracle WebLogic Server JDK, and set the PATH variable to include the path to the Oracle WebLogic Server bin directory for ant. On UNIX, use the export command. For example: Table 3–1 startManagedWebLogic Values Value Description managed_server The name of the Managed Server. For example: soa_server1 bam_server1 admin_url The URL of the Managed Server. For example: http:soahost:8001 http:soahost:9001 The port of the Managed Server for hosting SOA applications is typically 8001. The port of the Managed Server for Oracle BAM is typically 9001. username The Oracle WebLogic Server administrator. For example: weblogic password The password of the Oracle WebLogic Server administrator. For example: welcome1