-
Bug
-
Resolution: Done
-
Major
-
7.0.0
-
rhbas-7.0.0.ER1-business-central-eap7.zip
rhdm-7.0.0.ER1-decision-central-eap7.zip
-
User Experience
-
DR1
-
-
-
-
-
-
-
CR1
For earlier releases we had these properties commented out in standalone.xml files
in order to simplify the kie-server setup, but in latest build these are missing and setup of kie-server must be done using documentation.
These properties were present in LA builds.
Now they are not present.
Why were they removed? is there any particular reason or JIRA that I may have missed?
1) System property settings
<!--Please uncomment the following properties to make KIE Server to be managed by Business Central Please also uncomment the default user and password which defined in standalone/configuration/application-roles.properties and application-users.properties--> <!-- <property name="org.kie.server.location" value="http://localhost:8080/kie-execution-server/services/rest/server"/> <property name="org.kie.server.controller" value="http://localhost:8080/business-central/rest/controller"/> <property name="org.kie.server.controller.user" value="controllerUser"/> <property name="org.kie.server.controller.pwd" value="controllerUser1234;"/> <property name="org.kie.server.user" value="controllerUser"/> <property name="org.kie.server.pwd" value="controllerUser1234;"/> <property name="org.kie.server.id" value="default-kieserver"/> -->
2) Next, the subsystem for active-mq messaging disappeared from standalone.xml. Was it intended?
<subsystem xmlns="urn:jboss:domain:messaging-activemq:1.0"> <server name="default"> <security-setting name="#"> <role name="guest" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/> <role name="admin" delete-non-durable-queue="true" create-non-durable-queue="true" consume="true" send="true"/> </security-setting> <address-setting name="#" message-counter-history-day-limit="10" page-size-bytes="2097152" max-size-bytes="10485760" expiry-address="jms.queue.ExpiryQueue" dead-letter-address="jms.queue.DLQ"/> <http-connector name="http-connector" endpoint="http-acceptor" socket-binding="http"/> <http-connector name="http-connector-throughput" endpoint="http-acceptor-throughput" socket-binding="http"> <param name="batch-delay" value="50"/> </http-connector> <in-vm-connector name="in-vm" server-id="0"/> <http-acceptor name="http-acceptor" http-listener="default"/> <http-acceptor name="http-acceptor-throughput" http-listener="default"> <param name="batch-delay" value="50"/> <param name="direct-deliver" value="false"/> </http-acceptor> <in-vm-acceptor name="in-vm" server-id="0"/> <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/> <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/> <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/> <pooled-connection-factory name="activemq-ra" transaction="xa" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm"/> </server> </subsystem>
3) Missing additional login-module that should be present in all standalone*xml configuration files. Without this the connection between business-central and kie-server doesn't work. This piece applies only to RHBA distribution (RHDM doesn't have this login-module class so it would be impossible to login).
<security-domain name="other" cache-type="default"> <authentication> ... <login-module code="org.kie.security.jaas.KieLoginModule" flag="optional" module="deployment.business-central.war"/> </authentication> </security-domain>
