Administration scripts

Starting the servers actually means to start several server processes. The Node Managers should be configured as services on all platforms. On Windows this is configured automatically during the installation process, on Unix it is a manual step done after the installation. It is required to know about the different components in IFS Middleware Server and understand the difference between a Node Manager, an Admin Server and a Managed Server described here.  

NOTE: Compared to earlier releases of the Middle Tier Server it is not enough to simply stop the Windows services in order to stop the whole cluster! It will only stop the Node Managers but the Admin Server, the Managed Servers and the HTTP Server will still be running.

Overview

IFS Middleware Server can be administrated using scripts located in the <ifs_home>/ folder and the <ifs_home>/instance/<instance>/bin folder.

Contents

• Controlling the Clusters, Servers and Node Manager
• Check the Server Status
• Maintainance Mode
• Template for boot/shutdown on Unix types of OS
• Unix Script Usage Reference
• Create Cluster node
• Update HTTP Certificates

Controlling the Clusters, Servers and Node Manager

There are different types of servers and managers. Node Manager, Admin Server, Managed Servers and HTTP Server. All these can be controlled from one script.

The HTTP Server is controlled separately from the other servers. It is recommended to make sure that the Admin Server is running before attempting to start or stop a Managed Server, but the HTTP Server can be controlled without the Admin Server. Always make sure that the MWS Node Manager is running first.

The start and stop scripts will always prompt for the password.

Example:

Interactivly restart all targets: mws-srv.cmd
IFS Middleware Server Controller

Please specify action <START|STOP|STATUS|RESTAT|QUIT|MAINTAIN>: RESTART
Available targets:<all|node-managers|managed-servers|clusters|system-components>
node-managers:<ifshost01>
managed-servers:<AdminServer|MainServer1|IntServer1>
clusters:<main|integration>
system-components:<HttpServer1>
Please specify target: all
Password: abcd1234

This script might run into some problems in case some servers are in an incompatible state.

The mws-srv script will output some lines with internal information before showing the result of the given Action.

Check the Cluster or Server Status

It is possible to check the status of the cluster by using the mws-srv script. However, it will only check the status of the application server Node Manager, the Admin Server and the Managed Server(s).

The script will if possible give the current status of all servers, but if the Node Manager and the Admin Server is down, it is not possible for the script to get the status of the Managed Servers.

It is optional to use command line arguments.

Example:

Check status of the cluster:

mws-svr.cmd action=status target=all password=abcd1234

Result:

DOMAIN TEST - QUERY STATUS

AdminServer : RUNNING

Machine ifshost01
Node Manager (ifshost01) : RUNNING
main cluster
MainServer1 : RUNNING
integration cluster
IntServer1 : RUNNING

System Components
HttpServer1 : RUNNING

Maintainance Mode

While in maintenance mode, if the user access the landing page, then he will be directed in to https://<host>:<port>/maintenance.html page as given below. (eg: https://ifshost01.domain.com:58080/maintenance.html ).

 Example:

To start Maintainance Mode

Please specify action : MAINTAIN 
Password: abcd1234

Checking maintenance mode ...
Server is in production mode
Please specify maintenance action <START|STOP|STATUS>: start

Enter (comma separated) list of IPs or host names allowed to connect during maintenance mode: (default host)
OHS HttpServer1 started 
Server is in Maintenance Mode now. 


To exit Maintainance Mode
Please specify action : MAINTAIN
Password: abcd1234
Checking maintenance mode ...
Server is in maintenance mode
Please specify maintenance action <START|STOP|STATUS>: stop
OHS HttpServer1 started 
Server is in Production Mode now.

Silent
>mws-svr.cmd|sh action=maintain maintenance_args=start iplist=host.name password=pwd

Template for boot/shutdown Unix types of OS

A template for boot/shutdown is included as <ifs_home>/bin/ifsctl.sh.
This script should always be run as root .

Unix Script Usage Reference

This section is a reference of the capabilities, location, and names of the Unix version of the server scripts.

Boot/shutdown template script

Using systemctl

Instead of the above script, the nodemanager can be handled as a service using systemctl.

Install:

cp /bin/ifs@_.service /etc/systemd/system
systemctl daemon-reload
systemctl enable ifs@_.service
systemctl start/stop ifs@_.service

Uninstall:

systemctl disable ifs@_.service
rm /etc/systemd/system/ifs@_.service

Usage:

systemctl start ifs@_.service
systemctl stop ifs@_.service
systemctl restart ifs@_.service
systemctl status ifs@_.service

Update Cluster Node

Configure Cluster Nodes

Update HTTP Certificates

In order to make it more easy to work with the certificates a script is provided. The script will handle the web server (OHS) and middleware server (MWS) certificates by updating or extracting information. See link for more information.