此内容没有您所选择的语言版本。

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.5 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 
1

-Dorg.kie.server.id=myserver 
2

-Dorg.kie.server.user=process_server_username 
3

-Dorg.kie.server.pwd=process_server_password 
4

-Dorg.kie.server.controller=http://localhost:8080/business-central/rest/controller 
5

-Dorg.kie.server.controller.user=controller_username 
6

-Dorg.kie.server.controller.pwd=controller_password 
7

-Dorg.kie.server.location=http://localhost:8080/kie-server/services/rest/server 
8

-Dorg.kie.server.persistence.dialect=org.hibernate.dialect.PostgreSQLDialect 
9

-Dorg.kie.server.persistence.ds=java:jboss/datasources/psjbpmDS 
10
Copy to Clipboard Toggle word wrap
1
Start command with standalone-full.xml server 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/controller suffix
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
Note

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/server
Copy to Clipboard Toggle word wrap

If 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.

Note

When you use a class inside a dependency JAR file to access Process Server from Process Server client, you get the ConversionException and ForbiddenClassException in Business Central. To avoid generating these exceptions in Business Central, do one of the following:

  • If the exceptions are generated on the client-side, add following system property to the kie-server client:
System.setProperty("org.kie.server.xstream.enabled.packages", "org.example.**");
Copy to Clipboard Toggle word wrap
  • If the exceptions are generated on the server-side, open standalone-full.xml from the Red Hat Process Automation Manager installation directory, set the following property under the <system-properties> tag:
<property name="org.kie.server.xstream.enabled.packages" value="org.example.**"/>
Copy to Clipboard Toggle word wrap
  • Set the following JVM property:
-Dorg.kie.server.xstream.enabled.packages=org.example.**
Copy to Clipboard Toggle word wrap

It is expected that you do not configure the classes that exists in KJAR using these system property. Ensure that only known classes are used in the system property to avoid any vulnerabilities.

The org.example is an example package, you can define any package that you want to use. You can specify multiple packages separated by comma , for example, org.example1.* * , org.example2.* * , org.example3.* *.

You can also add specific classes , for example, org.example1.Mydata1, org.example2.Mydata2.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat