Deploying Node.js servers with Admin Center

You can use the Deploy tool to install Node.js servers as members of a collective. A Node.js collective member is called a Node.js server in this documentation.

1. Go to the Deploy tool.
   • From the Toolbox, select Deploy .
   • From details on hosts in the Explore tool, select Actions > one_or_more_host_names > Deploy Server Package.

   To directly launch the Deploy tool in the future, you can use the URL that is shown in the browser when you view the Deploy tool.

2. Select to install a Node.js application package.
   1. For DEFAULT SERVER TYPES, select Node.js.
   2. For DEFAULT RULES, select the Application Package default rule.
   3. Under APPLICATION PACKAGE, select CONFIRM.
3. For Deployment Parameters, specify the server package file to deploy, the server name, and the cluster name. If you drag a package to the Deploy tool or browse for a package, the server package file name value is set automatically. You can also type in a value. To specify a cluster name, you can select a cluster from a list of existing clusters or type in a new cluster name.
   • Drag or browse option

     To upload a file from your browser system to the collective controller, drag a package to the Deploy tool or browse for a package.

   • Use a file located on the collective controller option

     To use a file in the controller, the Node.js application must be available to the controller. If you have not done so already, complete step 2b in Deploying Node.js servers using deployment REST APIs. You then can use the Use a file located on the collective controller option.

     After you upload or drop a file, select Use a file located on the collective controller again to edit the Application directory field.

   Ensure that you run the wlpn-collective registerHost or wlpn-collective updateHost command with the same user as the user that you specify to deploy the member server. For example, if you run the command as the root user and then later deploy a member as a different user, the deployment fails. The failure occurs because the deployment service does not have rights to push a file to the /root/wlpn directory.

4. For Selected Hosts, select the host computers on which to install the server. If you do not see the wanted target host in the list of available hosts, you can search for a host.

   Each target host must be registered with the collective that is managed by Admin Center. For more information, see apiconnect-collective-member wlpn-server and wlpn-collective commands.

5. For Security Details, specify a password to protect newly generated keystore files that contain server authentication credentials.

   The product generates keystore files in the resources directory of each deployed server.

6. Select Deploy.