Connecting to an environment
The TrueSight Orchestration Development Studio application uses connections to establish communication with an environment. Connections are displayed in the environments pane of the Welcome page.
The following video (4:28) demonstrates how to connect Development Studio to a CDP.
To establish a connection to a CDP
- From the TrueSight Orchestration Development Studio Welcome page, click Connections.
Click
.
TrueSight Orchestration Development Studio creates a new connection with a default connection name. BMC recommends changing the connection name to a more descriptive name for your environment.Enter the authentication information:
Field
Description
Connection Name
Specifies the name for the connection.
User name
Specifies the account used to log on to the environment and configure the connection.
Users must have Grid Administration or Development Studio permissions. When TrueSight Orchestration Development Studio needs to connect to a grid, this name is the default used in the grid login dialog box.
Password
Specifies the password that corresponds to the user name.
Host Name/IP
Specifies the host name or IP address of the CDP server.
Port
Specifies the web server HTTPS port specified during the CDP server installation .
The default installation value is 38080.Protocol
Specifies the protocol used to retrieve the configuration file from the CDP server.
- Click Connect.
If the server has multiple IP addresses, an IP address window is displayed from which you select the IP address to use. - Click Close to exit the TrueSight Orchestration Development Studio Configuration window.
If you have any issues with the connection, see Troubleshooting-connection-problems for suggested solutions.
To delete a connection
- In the Connections List panel, select the connection to delete.
- Click Delete.
- Click OK to delete the connection.
If you attempt to delete the currently active connection, TrueSight Orchestration Development Studio warns you. Although you can delete the active connection, the workspace containing the run books, modules, and processes remains. You cannot export processes from the workspace until you connect to an environment.