Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Getting Started with Oracle WebLogic Server 12c: Developer's Guide

You're reading from   Getting Started with Oracle WebLogic Server 12c: Developer's Guide If you've dipped a toe into Java EE development and would now like to dive right in, this is the book for you. Introduces the key components of WebLogic Server and all that's great about Java EE 6.

Arrow left icon
Product type Paperback
Published in Sep 2013
Publisher Packt
ISBN-13 9781849686969
Length 374 pages
Edition 1st Edition
Languages
Arrow right icon
Toc

Table of Contents (18) Chapters Close

Getting Started with Oracle WebLogic Server 12c: Developer's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
1. Overview of WebLogic Server 12c and Related Technologies FREE CHAPTER 2. Setting Up the Environment 3. Java EE Basics – Persistence, Query, and Presentation 4. Creating RESTful Services with JAX-RS 5. Singleton Bean, Validations, and SOAP Web Services 6. Using Events, Interceptors, and Logging Services 7. Remote Access with JMS 8. Adding Security 9. Servlets, Composite Components, and WebSockets 10. Scaling Up the Application 11. Some WebLogic Internals Index

Introducing the Node Manager


One of the first changes we need to do in order to scale an application is to make the environment where it runs more flexible to accommodate the necessary changes, which usually involves creating WebLogic components such as clusters, servers, and machines. In order to interact with multiple (remote) machines, it's recommended that you set up the WebLogic Node Manager process. The Node Manager is a small Java process that runs standalone and can perform basic operations on WebLogic Server instances like start, stop, and restart.

Until Version 12.1.1, you could have only one Node Manager running on a specific machine and all requests to start or stop Managed Server applications from different domains were sent to it. The concept is really nice, having just one component running to deal with all resources available on that machine. But things would usually get tangled and this topology proved hard to maintain; for instance, different domains are managed by different...

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