We described multiple ways to start up the Oracle SOA Suite 12c environment. The command line, WLST, the console, or a combination of these can be utilized for both the infrastructure startup and shutdown.
The command line is possibly the quickest way to start up the infrastructure. It is also the simplest to script. All command-line instructions here are based on Linux but can be adapted to other operating systems with minor modifications.
Node Manager should be started up once per physical server. The following command dumps the output of both the standard out and standard error to the NodeManager.out log file. Log in to each node in your cluster and issue the following commands:
cd $DOMAIN_HOME/bin nohup ./startNodeManager.sh > NodeManager.out 2>&1 &
The AdminServer should be started only on a single host in the cluster and must be started via the command line (or WLST). The following command dumps both the standard output and standard error to the AdminServer.out log file. Log in to the server that hosts AdminServer and run the following commands:
cd $DOMAIN_HOME/bin nohup ./startWebLogic.sh > AdminServer.out 2>&1 &
The instructions mentioned in the following sections describe how to start up and shut down the SOA infrastructure in Linux using the bash shell. Your installation may (or may not) consist of multiple managed servers that include the SOA server, OSB server, BAM server, ESS server, and WSM server. Simply skip the components that are not installed in your domain. The instructions to do so are as follows:
Start up the SOA, OSB, BAM, ESS, and WSM managed servers on each node of the cluster, updating the highlighted managed server name, AdminServer hostname and port, and WebLogic username and password to reflect your environment:
cd $DOMAIN_HOME/bin nohup ./startManagedWebLogic.sh soa_server1 http://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > soa_server1.out 2>&1 & nohup ./startManagedWebLogic.sh osb_server1 http://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > osb_server1.out 2>&1 & nohup ./startManagedWebLogic.sh bam_server1 http://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > bam_server1.out 2>&1 & nohup ./startManagedWebLogic.sh ess_server1 http://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > ess_server1.out 2>&1 & nohup ./startManagedWebLogic.sh wsm_server1 http://adminhost:7001 -Dweblogic.management.username=weblogic -Dweblogic.management.password=welcome1 > wsm_server1.out 2>&1 &
Note
If the –Dweblogic.management arguments are not specified, you will be prompted to manually enter the username and password. If they are specified, be aware that the clear text password can be found logged in to the respective system's out file and process output list (for example, the ps command). If you have created and modified boot.properties in each of the managed servers, then these arguments may be skipped.
These commands dump the output to the respective .out log file, which can be viewed in real time as needed.
You must repeat the preceding commands for the other servers running in the cluster, modifying the managed server name accordingly (for example, soa_server2, soa_server3, and so on). You do not need to be logged in to those hosts as long as Node Manager is running on them, as the commands are sent to AdminServer, which then forwards them along to the appropriate host and managed server.
Unfortunately, it is not possible to completely start up the infrastructure through the console. After all, don't you need to start up the console first in order to allow you to bring up the remainder of the environment? Using the console to bring up your infrastructure requires starting up AdminServer and Node Manager on all target hosts.
Starting up Node Manager is a requirement if you intend to use the console to start up and shut down the managed servers. However, Node Manager must be started up either with the command line or through WLST. Later in this chapter, we will describe how to start up Node Manager through WLST. Simply run the following to start up Node Manager on each host using the command line:
cd $DOMAIN_HOME/bin nohup ./startNodeManager.sh > NodeManager.out 2>&1 &
Likewise, AdminServer must be started up before you bring up the rest of the infrastructure. The WebLogic Server Administration Console, which we utilize to bring up the remainder of the infrastructure, is targeted to AdminServer by default. If AdminServer is up, the WebLogic Server Administration Console is up. Simply run the following commands to bring up AdminServer:
cd $DOMAIN_HOME/bin nohup ./startWebLogic.sh > AdminServer.out 2>&1 &
Now that AdminServer is started, the WebLogic Server Administration Console is accessible. Here, you can manually start up each of the SOA, OSB, BAM, ESS, and WSM managed servers on each node of the cluster in a single shot.
To start up all managed servers, perform the following steps:
- Log in to the WebLogic Server Administration Console at
http://<adminhost>:7001/console. - Navigate to Servers | Control.
- Select the managed servers that you wish to start up.
- Click on Start. Refer to the following screenshot for an example.
Figure 3.2: Starting up the managed servers on the WebLogic Server Administration Console
Your installation may include MFT, and the instructions to start it up are not described here. Refer to the Oracle Fusion Middleware Using Oracle Managed File Transfer 12c Release 1 (12.1) for Windows or UNIX documentation from Oracle for more information.
WLST is another method to start up the infrastructure. Many administrators who come from a BEA background and have extensive experience with Oracle WebLogic Server tend to prefer WLST over the other approaches.
It is possible to use WLST to connect to and issue the commands to Node Manager or to connect to and issue commands to AdminServer. Both are acceptable, and the following instructions are specific to the latter.
As mentioned earlier, Node Manager can only be started up either with the command line or WLST. Simply run the following WLST command to start up Node Manager:
$WL_HOME/common/bin/wlst.sh startNodeManager()
In a clustered installation, AdminServer is started up on only one of the nodes of the cluster. The following WLST command starts up AdminServer:
$WL_HOME/common/bin/wlst.sh startServer('AdminServer', 'soa_domain', 't3://adminhost:7001', 'weblogic', 'welcome1', '/u01/oracle/products/Oracle_SOA1/user_projects/domains/soa_domain', 'true', 60000, 'false')
One way to start up the managed servers through WLST is by connecting and issuing the commands to Node Manager. Described in this section though is an alternate approach of connecting to AdminServer and issuing the commands to it instead. Regardless of which of these options you utilize, it is possible to start up all managed servers in a cluster or start up each managed server individually.
To start up any of the SOA, OSB, BAM, ESS, or WSM managed servers, use WLST to connect to AdminServer and then initiate the start commands for each managed server:
$WL_HOME/common/bin/wlst.sh wls:/offline> connect('weblogic', 'welcome1', 't3://adminhost:7001') wls:/soa_domain/serverConfig> start('soa_server1', 'Server') wls:/soa_domain/serverConfig> start('osb_server1', 'Server') wls:/soa_domain/serverConfig> start('bam_server1', 'Server') wls:/soa_domain/serverConfig> start('ess_server1', 'Server') wls:/soa_domain/serverConfig> start('wsm_server1', 'Server')
Alternatively, you can start up an entire cluster by issuing a single command as shown in the following code. Thus, all managed servers within that cluster are brought up with a single command:
wls:/soa_domain/serverConfig> start('soacluster', 'Cluster') wls:/soa_domain/serverConfig> start('osbcluster', 'Cluster') wls:/soa_domain/serverConfig> start('bamcluster', 'Cluster') wls:/soa_domain/serverConfig> start('esscluster', 'Cluster') wls:/soa_domain/serverConfig> start('wsmcluster', 'Cluster')