Encrypting A Default Username For stopServer.sh

By default ILMT, and WebSphere in general, asks you for a password when running srvstop.sh if security is enabled. That’s nice if you don’t trust your users. But, if you have a secured system you may not want to have to lookup the userid the once or twice a year you bring down WebSphere.

On a new install of ILMT, with the bundled WebSphere server, all you have to do is edit the soap.client.props file:

vi /opt/IBM/LMT/eWAS/profiles/AppSrv01/properties/soap.client.props

Example config.cerner file

Here is a sample config.cerner file for Cerner 2007 and newer with WebSphere 6. Their documentation is given in and image PDF, so you can’t copy the text out and typing this by hand is prone to errors. Replace DOMAIN, USER, and PASSWORD with the correct info.

# config.cerner
#
# last update: 1-23-2007
#

System {
	Enterprise {
		PrimaryDomain = "DOMAIN"
		Domain {
			cert {
				Principal {
					Authority {
						User = "USER"
						Password = "PASSWORD"
					}
				}
			}
		}
	}
	Coding {
		System {
			Instance {
				DOMAIN {
					Source = "EISService"
				}
			}
		}
	}
	Preferences {
		System {
			Instance {
				DOMAIN {
					Source = "Millennium"
				}
			}
		}
	}
	Application {
		MillenniumMobile {
			Authentication {
				ContainerHook {
					Host = "localhost"
					Context = "MillenniumMobile"
					Protocol = "http"
					Port = "9080"
				}
			}
		}
	}
}

Resync a node manually

To manually resync a node with the Deployment Manager, shutdown everything on that node and run the syncNode command.
Syntax:

syncNode.bat [options]

WebSphere 5:

syncNode.bat deploymgr 8889 -username username -password password

WebSphere 6:

syncNode.bat deploymgr 8879 -username username -password password

Remove a dead node

The cleanupNode command cleans up a node configuration from the cell repository. Only use this command to clean up a node if you have a node defined in the cell configuration, but the node no longer exists. You must run this command from the install_root/bin directory of a Network Deployment installation.
Note: The cleanupNode command may not remove application server information from clusters when the associated node has already been removed. In these cases, you will need to manually remove entries related to the server from WebSphere Application Server configuration files (cluster.xml, security.xml, multi-broker.xml, EAR deployment descriptors, for example).

Syntax:

Federate a node manually

To federate a node by hand, go to the app server bin directory and run addNode.bat.

Syntax:
addNode.bat [options]

WebSphere 5:

addNode.bat deploymgr 8889 -username username -password password

WebSphere 6:

addNode.bat deploymgr 8879 -username username -password password