Doorgaan naar hoofdcontent

BEA WebLogic: The NodeManager

The NodeManager is an important part of a weblogic server and this blog will give a short introduction and more detailed information on system administration can be found here.

Node Manager is a WebLogic Server utility that enables you to start, shut down, restart, and monitor remote WebLogic Server instances. To enable these capabilities, you run an instance of Node Manager on each physical machine in your domain.
WebLogic Server provides two versions of Node Manager, Java-based and script-based, with similar functionality. However, each version has different configuration and security considerations.
  • Java-based Node Manager runs within a Java Virtual Machine (JVM) process (start as a service). BEA provides native Node Manager libraries for Windows, Solaris, HP UX, Linux on Intel, Linux on Z-Series, and AIX operating systems.
  • A script based version is provideded for UNIX and Linux systems. This script is based on UNIX shell scripts, but uses SSH for increased security. SSH uses user-id based security.
Access Node Manager
The node manager can be accessed from:
  • Administration Server (Console or JMX utilities that you write)
  • WLST commands and scripts


What can you do with the Node Manager?
  • Start, Stop, Restart admin server
  • Start, shut down, suspend and restart Managed Servers
  • Monitor servers and view log files
    Node Manager creates a log file for the Node Manager process and a log file of server output for each server instance it controls.
Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h...
12 reacties
Meer lezen

Cloud to Cloud Application Integration

A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...
11 reacties
Meer lezen