Page Comparison

...

Using a custom port while running the MettleCI Setup Wizard

Create a file called setupEnv.sh in the root of /opt/dm/mci, add the following environment variable definition to this file and ensure it is owned by mciworb with permissions -rwxr-xr-x:

export JAVA_OPTS=-Ddw.server.applicationConnectors[0].port=<port-number>

Once /opt/dm/mci/setupEnv.sh has been created, restart MettleCI Workbench:

# restart the workbench servicesudoservice dm-mettleci-workbench stop sudoservice dm-mettleci-workbench start

The MettleCI Setup wizard will now be accessible via the specified port number.

Once the MettleCI Setup Wizard is complete, remove the updated setupEnv.sh file and complete the following section.

Changing ports after completing the MettleCI Setup wizard

You can request Workbench to operate on any ports you like by updating the following section in your <METTLECI-HOME-DIRECTORY>/config.yml file. This example exposes Workbench over HTTP on port 9090 and over HTTPS on port 9443:

server:
  applicationConnectors:
    - type: http
      port: 9090
    - type: https
      port: 9443
      keyStoreType: PKCS12
      keyStorePath: <path-to-keystore>
      keyStorePassword: <store-password>
      trustStoreType: PKCS12
      trustStorePath: <path-to-keystore>
      trustStorePassword: <store-password>

...

When HTTPS has been configured, the applicationConnector type will be HTTPS and there will be additional HTTPS specific properties, only update the port property.

Once you’ve made your changes restart your Workbench service using the Service Manager utility on Windows, or this command on Unix: .

...