ibmint create server command

You cannot use the ibmint create server command to create an independent integration server. For more information about creating an independent integration server, see Creating an integration server.

• Windows
• Linux®
• Linux on POWER®
• Linux on Z
• AIX®
• IBM z/OS® Container Extensions (zCX)

serverName

The name of the integration server.

You must specify at least one parameter to identify the target integration node in one of the following forms (a), (b), (c), (d), or (e):

(a)

--integration-node nodeName

The name of a locally defined integration node.

(b)

--integration-node-file filePath

This parameter identifies the name of a .broker file that contains the connection details for a remote integration node. Include the location (path) and file name when you specify this parameter. You must ensure that the location is accessible when you run this command.

Use this option if multiple users want to connect to the same integration node or integration server, or if you are using advanced connection parameters such as SSL. For more information, see Connecting to an integration node by creating a .broker file.

If you want to run a command that uses SSL to administer a remote integration node or integration server over a secured channel, you must specify the keystore and truststore password for the connection that is using the IBM_JAVA_OPTIONS environment variable. For more information, see Resolving problems when running commands.

You cannot use --integration-node and --integration-node-file in the same command.

(c)

--integration-node nodeName --admin-host host --admin-port port

These parameters identify the nodeName, host, and port of a remote integration node, for connections that do not require advanced connection parameters.

• --integration-node nodeName: This parameter is optional for validation.
• --admin-host: The hostname or IP address of the computer on which the integration node is running.
• --admin-port port: The port on which the web user interface HTTP connection listener is listening.

(d)

--admin-uri URI

The URI of a remote integration server, in the form tcp://[user[:password]@]host:port. You can optionally specify the --integration-node parameter for validation with --admin-uri.

If you want to connect to a secured integration node as a specific user, provide the security credentials as a URI in the following format: tcp://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.

(e)

--admin-uri URI --cacert cacertFile --cacert-password cacertPassword

The URI of a remote integration server, in the form ssl://[user[:password]@]host:port. Optionally followed by options concerning REST communications.

If you want to connect to an integration server over a secure connection, you can use the --cacert parameter to specify the path to a certificate file (in either PEM, P12, or JKS format) and the --cacert-password parameter to specify the password for password-protected cacert files.

If you want to connect to a secured integration node as a specific user, provide the security credentials as a URI in the following format: tcp://user:password@hostname. If your password contains URI Reserved characters, you must convert these characters to the percent-encoded format. For more information, see A correct URL and password returns error BIP1939 when you attempt to connect to a remote host name in Resolving problems when running commands.

--https

(Optional) Specifies that HTTPS will be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.

--no-https

(Optional) Specifies that HTTPS will not be used for the connection to the integration node or server. If neither --https nor --no-https is specified, the connection is tried first with HTTPS and then without using HTTPS if the first attempt fails.

--cacert cacertFile

(Optional) Specifies the path to the certificate file (in either PEM, P12, or JKS format) to be used to verify the integration node or server. If no cacert file is specified and default admin-ssl is enabled, the cacert file defaults to the default pem file for admin-ssl.

• The --cacert parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --cacert when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
• The --cacert parameter can be set only if the --admin-host parameter is specified, or if the --admin-uri parameter is specified with a URI that starts with ssl://.

--cacert-password cacertPassword

(Optional) The password for password-protected cacert files.

• The --cacert-password parameter is valid only if HTTPS is used for the connection and if the --cacert parameter has been set. You cannot set it together with the --no-https parameter.
• The --cacert-password parameter can be set only if the --admin-host parameter is specified, or if the --admin-uri parameter is specified with a URI that starts with ssl://.

--insecure

(Optional) Specifies that the certificate that is returned by the integration node or server will not be verified.

• The --insecure parameter is valid only if HTTPS is used for the connection, so it cannot be set together with the --no-https parameter. You can set --insecure when the --https parameter has been set or when neither the --https nor --no-https parameter has been set (in which case SSL is used by default).
• The --insecure parameter can be set only if the --admin-host parameter is specified, or if the --admin-uri parameter is specified with a URI that starts with ssl://.

--timeout-seconds seconds

The maximum number of seconds to wait for the integration server to be started (default is 60).

--trace filePath

(Optional) Use this parameter to send verbose internal trace to the specified file.

--help

(Optional) Use this parameter to display help information about the command.