Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle SOA Suite 12c Administrator's Guide

You're reading from   Oracle SOA Suite 12c Administrator's Guide A guide to everything an Oracle SOA Suite 12c administrator needs to hit the ground running

Arrow left icon
Product type Paperback
Published in Nov 2015
Publisher
ISBN-13 9781782170860
Length 456 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (14) Chapters Close

Preface 1. SOA Infrastructure Management – what You Need to Know FREE CHAPTER 2. Navigating Enterprise Manager Fusion Middleware Control 12c 3. Startup and Shutdown 4. Managing Services 5. Deploying Code 6. Monitoring Oracle SOA Suite 12c 7. Configuration and Administration 8. Managing the Database 9. Troubleshooting the Oracle SOA Suite 12c Infrastructure 10. Backup and Recovery 11. Introducing Oracle Enterprise Scheduler 12. Clustering and High Availability 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image