Due to a known issue do not use JDK1.8.0_151 with WSO2 products. Use JDK 1.8.0_144 until JDK 1.8.0_162-ea is released.
This documentation is for WSO2 Data Services Server version 3.5.1. For the latest documentation, see the documentation for WSO2 Enterprise Integrator.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info
titleStarting the server as a Worker Node:

If you want to provide access to the production environment without allowing any user group (including admin) to log in to the management console, you must start the product as a worker node. You can enable the worker node for your product in two ways:

1. Use the -DworkerNode startup command when you start the product as shown below:

  • On Windows: <PRODUCT_HOME>\bin\wso2server.bat --run -DworkerNode
  • On Linux/Solaris: sh <PRODUCT_HOME>/bin/wso2server.sh -DworkerNode

2.You can set permanently set the -DworkerNode system property to 'true' in your product startup script. When you execute the product startup script, the worker profile will be started automatically.

Code Block
'-DworkerNode=false'

Note that this profile only consists of the back-end features of the Application Server and does not include stubs or any UI features. However, in WSO2 AS, if you require any stubs to be activated in addition to the back-end features when you run the worker profile, you can manually add the relevant JARs to the web application's lib folder before starting the server. For information about other profiles available for AS, see Running the Product on a Preferred Profile.

If you want to check any additional options available to be used with the startup commands, type -help after the command, such as: sh <PRODUCT_HOME>/bin/wso2server.sh -help.

...