このコンテンツは選択した言語では利用できません。
Chapter 4. Red Hat JBoss EAP Migration
4.1. Migrating Red Hat JBoss BPM Suite from Red Hat JBoss EAP 6.4.x to 7.0
Deploying Red Hat JBoss BRMS or Red Hat JBoss BPM Suite on Red Hat JBoss EAP 7 requires changes to the project BOM files. To upgrade your container from Red Hat JBoss EAP 6.4 to Red Hat JBoss EAP 7, configure the Intelligent Process Server or the Realtime Decision Server in the following way:
-
If using JMS, change the provider URL(
java.naming.provider.url) forInitialContext, which is used to look up JMS queues. Change the remoting port from4447to8080(EAP 7 useshttp-remoting). For example:
final Properties env = new Properties();
...
env.put(Context.PROVIDER_URL, "http-remoting://<server ip>:8080");
...
InitialContext context = new InitialContext(env);Additionally, change the JMS dependency BOM to:
<dependency>
<groupId>org.jboss.eap</groupId>
<artifactId>wildfly-jms-client-bom</artifactId>
<version>7.0.2.GA-redhat-1</version>
<type>pom</type>
</dependency>-
If using remote JMS client for Business Central, change the protocol from
remotetohttp-remotingand port from4447to8080. Also, use ActiveMQ Artemis client library (org.apache.activemq:artemis-jms-clientartifact).
For more information on migration from Red Hat JBoss EAP 6.4 to Red Hat JBoss EAP 7.0, see the Application Migration Changes chapter of the Red Hat JBoss EAP Migration Guide.
