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 Deprecated featurestartOgServer or [Version 8.6 and later]startXsServer command.

[Version 8.6 and later]

About this task

[Version 8.6 and later]Deprecated featureDeprecated: The startOgServer and stopOgServer commands start servers that use the Object Request Broker (ORB) transport mechanism. The ORB is deprecated, but you can continue using these scripts if you were using the ORB in a previous release. The IBM eXtremeIO (XIO) transport mechanism replaces the ORB. Use the startXsServer and stopXsServer scripts to start and stop servers that use the XIO transport.

Procedure

  • Start secure container servers.

    Starting a secure container server requires the following security configuration file:

    • Server property file: The server property file configures the security properties specific to the server. Refer to the Server properties file for more details.
    Specify the location of this configuration file by providing the following argument to the startOgServer [Version 8.6 and later]or startXsServer script:
    -serverProps
    Specifies the location of the server property file, which contains the server-specific security properties. The file name specified for this property is in plain file path format, such as ../security/server.properties.
    Enter the following lines when you run the startOgServer command [Version 8.6 and later]or startXsServer command:[Linux][Unix]
    startOgServer.sh <arguments> -jvmargs -Djava.security.auth.login.config=jaas.config 
    -Djava.security.manager -Djava.security.policy="auth.policy" -Dobjectgrid.home=$OBJECTGRID_HOME
    [Version 8.6 and later][Linux][Unix]
    startXsServer.sh <arguments> -jvmargs -Djava.security.auth.login.config=jaas.config 
    -Djava.security.manager -Djava.security.policy="auth.policy" -Dobjectgrid.home=$OBJECTGRID_HOME
    [Windows]
    startOgServer.bat <arguments> -jvmargs -Djava.security.auth.login.config=jaas.config 
    -Djava.security.manager -Djava.security.policy="auth.policy" -Dobjectgrid.home=%OBJECTGRID_HOME%
    [Version 8.6 and later][Windows]
    startXsServer.bat <arguments> -jvmargs -Djava.security.auth.login.config=jaas.config
     -Djava.security.manager -Djava.security.policy="auth.policy" -Dobjectgrid.home=%OBJECTGRID_HOME%
  • Start secure catalog servers.
    To start a secure catalog service, you must have the following configuration files:
    • Security descriptor XML file: The security descriptor XML file describes the security properties common to all servers, including catalog servers and container servers. One property example is the authenticator configuration which represents the user registry and authentication mechanism.
    • Server property file: The server property file configures the security properties that are specific to the server.
    Specify the location of these configuration files by providing the following arguments to the startOgServer [Version 8.6 and later]or startXsServer script:
    -clusterSecurityFile and -clusterSecurityUrl
    These arguments specify the location of the Security descriptor XML file. Use the -clusterSecurityFile parameter to specify a local file, or the -clusterSecurityUrl parameter to specify the URL of the objectGridSecurity.xml file.
    -serverProps
    Specifies the location of the server property file, which contains the server-specific security properties. The file name specified for this property is in plain file path format, such as c:/tmp/og/catalogserver.props.