For LINUX platforms[16.0.0.3 and later]

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.

Before you begin

  • Create a Liberty collective that includes the hosts to which you plan to install the Node.js server. See the Before you begin section of Deploying resources with Admin Center and the Configuring a Liberty collective topic.
  • Complete the Before you begin section and steps 1-4 in Deploying Node.js servers using deployment REST APIs. You do not need to complete step 2b unless the Node.js application is located on the collective controller.
  • If you want to upload the Node.js application from your browser system to the collective controller on the Deployment Parameters panel in step 3, add to the controller server.xml file a remoteFileAccess statement that enables write access to the location; for example:
    <remoteFileAccess writeDir="/home/uploadDir/>
    This statement is required even if you have specified host write paths with --hostWritePath in the registerHost or updateHost command on the controller host.

About this task

After you install Node.js, configure the Liberty collective, and register the target host, use the Deploy tool to install the Node.js server as a member of the collective.

Procedure

  1. Go to the Deploy tool.
    • From the Toolbox, select Deploy icon.
    • From details on hosts in the Explore tool, select Actions icon > 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 viewing the Deploy tool.

  2. Select to install a Node.js application package.
    1. For DEFAULT SERVER TYPES, select Node.js.
    2. Under NODE.JS SERVER, select NEXT.
    3. For DEFAULT RULES, select the Application Package default rule.
    4. Under APPLICATION PACKAGE, select NEXT.
    5. 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, directory and server package file name values are set automatically. You can also type in the values.
    • Drag or browse option

      To upload a file from your browser system to the collective controller, add to the controller server.xml file a statement that enables write access:

      <remoteFileAccess writeDir="/home/uploadDir"/>

      You then can 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.

  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. See Registering host computers with a Liberty collective.

  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.

Results

The Deploy action runs. The Deploy tool displays messages about deployment status and results.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: Thursday, 8 September 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-libcore-mp&topic=twlp_ui_deploy_nodejs
File name: twlp_ui_deploy_nodejs.html