Running the Product

The following sections describe how to run WSO2 Enterprise Integrator (WSO2 EI).

1 Starting the ESB profile
2 Starting the Business Process profile
3 Starting the Message Broker profile
4 Starting the MSF4J profile
5 Starting the Analytics profile
6 Stopping a profile
7 Running WSO2 Enterprise Integrator via Tooling
8 Working with the Management Console

Starting the ESB profile

If you are using IBM JDK 1.8, change the value of the org.owasp.csrfguard.PRNG.Provider property to 'IBMJCE' in the <EI_HOME>/conf/security/Owasp.CsrfGuard.Carbon.properties file.
The data integration functionalities of WSO2 EI comes with the ESB profile. Therefore, you need to start the ESB profile to use them.

Open a command prompt (or a shell in Linux) and go to the <EI_HOME>\bin directory.
Execute one of the following commands:
- To start the ESB profile in a typical environment:
  - On Windows:integrator.bat --run
  - On Linux/Mac OS:sh integrator.sh
- To start the ESB profile in the background mode of Linux: sh integrator.sh start
  To stop the ESB profile running in this mode: sh integrator.sh stop
- To provide access to the production environment without allowing any user group (including admin) to log in to the Management Console:
  - On Windows: integrator.bat --run -DworkerNode
  - On Linux/Mac OS: sh integrator.sh -DworkerNode
- To check for additional options you can use with the startup commands, type -help after the command, such as:
  sh integrator.sh -help.
The operation log keeps running until the ESB profile starts, which usually takes several seconds. Wait until theESB profile fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."
- Open the ESB Management Console using https://localhost:9443/carbon, and log in using admin as the username as well as the password.

You can start the other profiles of WSO2 EI by executing the following scripts in the <EI_HOME>/bin directory in a Command Prompt.

Profile	On Windows	On Linux/Mac OS:

Profile	On Windows	On Linux/Mac OS:
Business Process	`business-process.bat`	`business-process.sh`
Message Broker	`broker.bat`	`broker.sh`
MSF4J	`msf4j.bat`	`msf4j.sh`
Analytics	`analytics.bat`	`analytics.sh`

Alternatively, you can start profiles other than the ESB profile of WSO2 EI as described below.

Starting the Business Process profile

If you are using IBM JDK 1.8, change the value of the org.owasp.csrfguard.PRNG.Provider property to 'IBMJCE' in the <EI_HOME>wso2/business-process/conf/security/Owasp.CsrfGuard.Carbon.properties file.

Open a command prompt (or a shell in Linux) and go to the <EI_HOME>\wso2\business-process\bin directory.
Execute one of the following:
- On Linux/Mac OS: sh wso2server.sh
- On Windows: wso2server.bat
The operation log keeps running until the Business Process profile starts, which usually takes several seconds. Wait until the Business Process profile fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."
- Open the Business Process Management Console using https://localhost:9445/carbon, and log in using admin as the username as well as the password.
- Open the BPMN Explorer using https://localhost:9445/bpmn-explorer, and log in using admin as the username as well as the password.
- Open the Human Task Explorer using https://localhost:9445/humantask-explorer, and log in using admin as the username as well as the password.

Starting the Message Broker profile

If you are using IBM JDK 1.8, follow the steps below to start the message broker profile.

Replace all the 'SunX509' entries in the <EI_HOME>/wso2/broker/conf/broker.xml file with 'IbmX509' as follows:
<sslConnection enabled="true" port="8672"> <keyStore> <location>repository/resources/security/wso2carbon.jks</location> <password>wso2carbon</password> <certType>IbmX509</certType> </keyStore> <trustStore> <location>repository/resources/security/client-truststore.jks</location> <password>wso2carbon</password> <certType>IbmX509</certType> </trustStore> </sslConnection>
Change the value of the org.owasp.csrfguard.PRNG.Provider property to 'IBMJCE' in the <EI_HOME>wso2/broker/conf/security/Owasp.CsrfGuard.Carbon.properties file.

Open a command prompt (or a shell in Linux) and go to the <EI_HOME>\wso2\broker\bin directory.
Execute one of the following:
- On Linux/Mac OS:sh wso2server.sh
- On Windows:wso2server.bat
The operation log keeps running until the Message Broker profile starts, which usually takes several seconds. Wait until the Message Broker profile fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."
- Open the Message Broker Management Console using https://localhost:9446/carbon, and log in using admin as the username as well as the password.

Starting the MSF4J profile

Before starting the MSF4J profile, copy the JAR files of your services to the <EI_HOME>/wso2/msf4j/deployment/microservices/ directory.
If you are using IBM JDK 1.8, change the value of the org.owasp.csrfguard.PRNG.Provider property to 'IBMJCE' in the <EI_HOME>/conf/security/Owasp.CsrfGuard.Carbon.properties file.

Open a command prompt (or a shell in Linux) and go to the <EI_HOME>\wso2\msf4j\bin directory.
Execute one of the following:
- On Linux/Mac OS: sh carbon.sh
- On Windows: carbon.bat
The operation log keeps running until the MSF4J profile starts, which usually takes several seconds. Wait until the MSF4J profile fully boots up and displays a message similar to "WSO2 Carbon started in n seconds."

For more information on sample use cases of MSF4J, see the WSO2 MSF4 GitHub Documentation.