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 /setupEnv.sh
containing a line of the following format:
Code Block |
---|
export JAVA_OPTS=-Ddw.server.applicationConnectors[0].port=<port-number> |
Ensure the file is owned by mciworb
with and has permissions 755 (-rwxr-xr-x
:
...
). For example,
Code Block |
---|
$> sudo chmod 755 /opt/dm/mci/setupEnv.sh $> sudo chown mciworkb /opt/dm/mci/setupEnv.sh $> ls -l /opt/dm/mci/setupEnv.sh -rwxr-xr-x 1 mciworkb dstage 64 Sep 30 09:02 /opt/dm/mci/setupEnv.sh $> cat /opt/dm/mci/setupEnv.sh export JAVA_OPTS=-Ddw.server.applicationConnectors[0].port=<port-number>5678 $> |
Once /opt/dm/mci/setupEnv.sh
has been created , restart MettleCI Workbenchyour Workbench service using the Service Manager utility on Windows, or this command on Unix:
Code Block | ||
---|---|---|
| ||
$> sudo service dm-mettleci-workbench restart |
The MettleCI Setup wizard discover this file and will now be accessible via the specified port number (5678
in the example above).
Once the MettleCI Setup Wizard is complete, remove delete the updated setupEnv.sh
file and complete the steps in the following section.
Changing ports after completing the MettleCI Setup wizard
...
Code Block | ||
---|---|---|
| ||
server: applicationConnectors: - type: http port: 9090 |
When HTTPS has been configured, the applicationConnector
type will be HTTPS
and there the server section will be contain additional HTTPS-specific properties, . You should only update the HTTPS port
property, leaving the other values unchanged.
Once you’ve made your changes restart your Workbench service using the Service Manager utility on Windows, or this command on Unix: .
...