Book Image

Oracle SOA Suite 12c Administrator's Guide

Book Image

Oracle SOA Suite 12c Administrator's Guide

Overview of this book

Oracle SOA Suite 12 c is the most comprehensive and integrated infrastructure on the market today that is used for building applications based on service-oriented architecture. With the vast number of features and capabilities that Oracle SOA Suite 12c has to offer comes numerous complexities and challenges for administration. Oracle SOA Suite 12c Administrator's Guide covers all the core areas of administration needed for you to effectively manage and monitor the Oracle SOA Suite environment and its transactions, from deployments, to monitoring, to performance tuning, and much, much more. Manage, monitor, and troubleshoot SOA composites and OSB services from a single product set. Understand core administrative activities such as deployments, purging, startup and shutdown, configuration, backup, and recovery. Also learn about new features such as Oracle Enterprise Scheduler, lazy loading, work manager groups, high availability, and more.
Table of Contents (19 chapters)
Oracle SOA Suite 12 Administrator's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Starting up the infrastructure


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.

Using the command line

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.

Starting up Node Manager

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 &

Starting up AdminServer

The AdminServer should be started only on a single host in the cluster and must be started via the command line (or WLST). The...