Setting up a convenient way to deploy a solution

You can create a reusable deployment configuration from the solution map to deploy your solution to a test server. After you complete the server connection details, you can also manage your connectivity configurations from the same wizard.

1. In the solution map, click Manage deployment configurations, or right-click a solution and click Deploy > Deployment Configurations.
2. In the Deployment configurations wizard, either click New and enter a unique configuration name, or select an existing deployment configuration.
3. Select a Local or Remote server.
4. If you select a Local server, you must specify a server name or select an existing server name from the menu. Local servers are configured in the Servers view.

   The path to the administrator toolkit is completed automatically if you select a server from the menu. If you do not have a local server that is configured in the Servers view, enter the name of a local server, and enter the path to your administrator toolkit. The default administrator toolkit path is <InstallDir>/runtime/ia/bin.

5. Click Next.
6. Specify the Java™ Management Extensions (JMX) connection properties for the server, or select Use existing properties file to use the connection properties in an existing file. By default, the fields in this wizard use the values in the <InstallDir>/runtime/ia/etc/connection.properties file.
   1. Specify a value for host. The default host name for cisDev is localhost.
   2. Specify a value for port. The default port value for cisDev is 9443.
   3. Specify the user name and password of a user who has the administrator role. The default name and password for cisDev is tester.
   4. Optional: Specify the location and password for the truststore (javax.net.ssl.trustStore). The truststore contains certificate authorities that you trust. The default location is ${wlp.user.dir}/servers/cisDev/resources/security/key.jks.
   5. Optional: Specify the location and password for the keystore. A keystore contains private keys for client authentication. If you do not specify values, the keystore is not used.
   6. Specify the SSL protocol for the connection. The default value is TLSv1.2 (Transport Layer Security).
   7. Optional: Select Disable SSL hostname verification to disable the SSL protocol for the connection. You might want to disable the SSL host name verification if the certificate has a host name that is different from the host name to which you are connecting. For example, you might disable the SSL protocol if the certificate is signed "localhost" and you want to connect to an IP address.
   8. Optional: If you do not want the client to check whether the certificate presented by the server is trusted, select Disable server certificate verification. If you select this option and the server is not trusted, authentication credentials and other user information might be passed on through the JMX connection.
   If you have a connectivity definition in your solution, click Next to configure the connectivity assets.
7. Optional: Create a connectivity configuration, or modify an existing one.
   1. On the connectivity configuration page, choose to create a new file or import an existing file, and then click Next.
   2. Select the inbound and outbound endpoints that you want to configure, and then click Next.
   3. Complete the fields to configure the endpoints that you selected.
8. Click Finish. The wizard prompts you to deploy your solution. Click Yes to deploy or No to exit the wizard without deploying the solution.

   If you deploy your solution, the solution archive and any connectivity configuration are deployed to the server. If your deployment contains a connectivity configuration, the connectivity configuration file opens in the XML editor.