crmdown shuts down the CRM specified on the command line. It can be used from any machine located on the same TCP/IP network as the machine running the CRM server. It can be used in a script and will return 0 if the command could be sent to the target CRM. It will return 1 if the command could not be sent to the target CRM.

-n

Names the machine and port running the CRM server.

-v

Specifies verbose. Normally the command will not produce any messages, facilitating use in a script.

-i

Ignores errors.

-u

Establishes that process authentication is in effect for communications between this process and the CRM.

<keyfile>

Is the location of a file containing a hash key known to both this process and the CRM. The file contains a single line specifying a unique hash key (limited to eight characters). The file should be protected.

-S <ssl_config_file>

Indicates the path to a file that contains SSL configuration, similar to ubbconfig. The following settings must be included in this file:

• The principal name of the Oracle SSL wallet: SEC_PRINCIPAL_NAME=ISH_tuxqa
• The location of Oracle SSL wallet: SEC_PRINCIPAL_LOCATION=/scratch/username/CRM/bin/wallet
• The wallet password: SEC_PRINCIPAL_PASSVAR=abcd1234
• Set the SSL trace level: SEC_TRACE_LEVEL=3

-N <type>:<min>:<max>

Establishes that encryption is in effect for this process. Encryption type, currently, the valid entries are GPE (for general purpose encryption) and SSL.

For GPE:

min Designates the minimum number of bits to be used for encryption. These levels are used during the negotiation between the CRM and client process. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128.

max Designates the maximum number of bits to be used for encryption. These levels are used during the negotiation between the CRM and client process. Any number is acceptable, but the negotiated values resolve to 0, 56, or 128

For SSL:

min Determines the minimum number of bits of cipher suite to be used for SSL encryption. They are used during the SSL negotiation between the CRM and GWSNAX. It must be less than or equal to 256. The negotiated values resolve to 128 or 256. The strongest supported cipher suite is used finally.

max Determines the maximum number of bits of cipher suite to be used for SSL encryption. They are used during the SSL negotiation between the CRM and GWSNAX. The negotiated values resolve to 128 or 256. The strongest supported cipher suite is used finally.