Starting and stopping secure servers

Security is enabled by specifying security-specific configurations when you start and stop servers.

Starting secure servers in a stand-alone environment
To start secure stand-alone servers, you pass the proper configuration files by specifying parameters on the startOgServer or startXsServer command.
Starting secure servers in WebSphere Application Server
To start secure servers in WebSphere Application Server, you must specify the security configuration files in the generic Java virtual machine (JVM) arguments.
Stopping secure servers
Stopping secure catalog servers or container servers requires one security configuration file.

Starting secure servers in a stand-alone environment
To start secure stand-alone servers, you pass the proper configuration files by specifying parameters on the startOgServer or startXsServer command.
Starting and stopping secure servers in the Liberty profile
Use the start command to start secure servers in the Liberty
Starting and stopping secure servers in the OSGi framework
To start secure stand-alone servers in the Eclipse Equinox OSGi framework, pass the proper configuration files by specifying parameters from the command line.
Starting secure servers in WebSphere Application Server
To start secure servers in WebSphere Application Server, you must specify the security configuration files in the generic Java™ virtual machine (JVM) arguments.
Stopping secure servers
Stopping secure catalog servers or container servers requires one security configuration file.

Parent topic: [Version 8.6 and later]

Scenario: Securing your data grid in eXtreme Scale

Previous topic: [Version 8.6 and later]

Storing security artifacts for authorized users

Parent topic: Security

Related tasks

Configuring WebSphere Application Server applications to automatically start container servers

Last updated: 2021-03-29