红帽全球峰会此内容没有您所选择的语言版本。
Chapter 4. Configuring and starting Process Server
You can configure your Process Server location, user name, password, and other related properties by defining the necessary configurations when you start Process Server.
Procedure
Navigate to the Red Hat Process Automation Manager 7.1 bin directory and start the new Process Server with the following properties. Adjust the specific properties according to your environment.
$ ~/EAP_HOME/bin/standalone.sh --server-config=standalone-full.xml
-Dorg.kie.server.id=myserver
-Dorg.kie.server.user=process_server_username
-Dorg.kie.server.pwd=process_server_password
-Dorg.kie.server.controller=http://localhost:8080/business-central/rest/controller
-Dorg.kie.server.controller.user=controller_username
-Dorg.kie.server.controller.pwd=controller_password
-Dorg.kie.server.location=http://localhost:8080/kie-server/services/rest/server
-Dorg.kie.server.persistence.dialect=org.hibernate.dialect.PostgreSQLDialect
-Dorg.kie.server.persistence.ds=java:jboss/datasources/psjbpmDS - 1
- Start command with
standalone-full.xmlserver profile - 2
- Server ID that must match the server configuration name defined in Business Central
- 3
- User name to connect with Process Server from the Process Automation Manager controller
- 4
- Password to connect with Process Server from the Process Automation Manager controller
- 5
- Process Automation Manager controller location, Business Central URL with
/rest/controllersuffix - 6
- User name to connect to the Process Automation Manager controller REST API
- 7
- Password to connect to the Process Automation Manager controller REST API
- 8
- Process Server location (on the same instance as Business Central in this example)
- 9
- Hibernate dialect to be used
- 10
- JNDI name of the data source used for your previous Red Hat JBoss BPM Suite database
If Business Central and Process Server are installed on separate application server instances (Red Hat JBoss EAP or other), use a separate port for the Process Server location to avoid port conflicts with Business Central. If a separate Process Server port has not already been configured, you can add a port offset and adjust the Process Server port value accordingly in the Process Server properties.
Example:
-Djboss.socket.binding.port-offset=150
-Dorg.kie.server.location=http://localhost:8230/kie-server/services/rest/serverIf the Business Central port is 8080, as in this example, then the Process Server port, with a defined offset of 150, is 8230.
Process Server connects to the new Business Central and collects the list of deployment units (KIE containers) to be deployed.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}