Installing the Bonita BPM subscription server manually (deprecated)
- Data Fabric
- MDM Platform
You can install the Bonita BPM subscription server (Tomcat bundle) and integrate it with Talend MDM Server manually.
Procedure
- Download the archive file of the Bonita BPM subscription server 7.9.0 compatible with your product from https://www.bonitasoft.com/downloads, for example, BonitaSubscription-7.9.0-tomcat.
- Unzip the Bonita BPM server archive file into a local directory which will be referred to as <Bonita_Home>.
-
Browse to the file server.xml under the directory
<Bonita_Home>\server\conf, and edit the file
to set up the port, protocol, and other information for the Bonita BPM server and
save your changes.
An example of the configuration is shown below:
<Connector port="8280" protocol="HTTP/1.1" connectionTimeout="20000" maxThreads="20" redirectPort="8443" maxPostSize="-1" URIEncoding="UTF-8"/>
For more information, see Apache Tomcat 9 Configuration Reference.
-
Browse to the directory
<$INSTALLDIR>\bonita\engine-client\conf (<$INSTALLDIR> specifies the path where the
Talend MDM Server has been installed), and update
the file bonita-client-custom.properties
under the directory according to your actual situation, which allows the
Talend MDM Server to connect to the Bonita BPM
server correctly.
An example of the file is shown below:
org.bonitasoft.engine.api-type = HTTP server.url = http://localhost:8280 application.name = bonita
The property server.url must use the host name or IP address of the actual machine that hosts the Bonita BPM server and use the port number for the Bonita BPM server that is configured in server.xml.
-
Create a folder mdm
under the directory
<Bonita_Home>\setup, and then create a file
mdm.conf under that folder with the
following content, which allows the Bonita BPM server to connect to the Talend MDM Server correctly.
admin.user=admin admin.password=talend mdm.endpoint.url=http://localhost:8180/talendmdm/services/soap
The property mdm.endpoint.url must use the host name or IP address of the actual machine that hosts the Talend MDM Server and use the port number that corresponds to the chosen HTTP port for the Talend MDM Server during installation. By default, it is 8180.
-
Enable two properties SECURITY_OPTS and
CATALINA_OPTS in the file
<Bonita_Home>\server\bin\setenv.bat and update their
values to:
rem Optional JAAS configuration. Usually used when delegating authentication to LDAP / Active Directory server set SECURITY_OPTS="-Djava.security.auth.login.config=%CATALINA_HOME%\conf\jaas-standard.cfg" rem Pass the JVM system properties to Tomcat JVM using CATALINA_OPTS variable set CATALINA_OPTS=%CATALINA_OPTS% %PLATFORM_SETUP% %H2_DATABASE_DIR% %DB_OPTS% %BDM_DB_OPTS% %ARJUNA_OPTS% %INCIDENT_LOG_DIR% %SECURITY_OPTS% -Dfile.encoding=UTF-8 -Xshare:auto -Xms1024m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError
-
Update the file
<Bonita_Home>\server\conf\jaas-standard.cfg
with the following content:
BonitaAuthentication-1 { org.talend.mdm.bonita.server.jaas.MDMLoginModule required; };
- Extract the file bonita.war under the directory <Bonita_Home>\server\webapps to <Bonita_Home>\server\webapps\bonita.
-
Extract the XML file bonita-tenant-community.xml from the JAR file
<Bonita_Home>\server\webapps\bonita\WEB-INF\lib\bonita-server-7.9.0.jar,
replace the definition of the bean authenticationService and
operationService with the following code, and save the file
to the directory
<Bonita_Home>\server\webapps\bonita\WEB-INF\classes.
<bean id="authenticationService" class="org.talend.mdm.bonita.server.jaas.MDMAuthenticationService"> <constructor-arg name="logger" ref="tenantTechnicalLoggerService" /> <constructor-arg name="sessionAccessor" ref="sessionAccessor" /> </bean>
<bean id="operationService" class="org.talend.mdm.bonita.engine.core.operation.impl.MDMOperationServiceImpl"> <constructor-arg name="operationExecutorStrategyProvider" ref="operationExecutorStrategyProvider" /> <constructor-arg name="leftOperandHandlerProvider" ref="leftOperandHandlerProvider" /> <constructor-arg name="expressionResolverService" ref="expressionResolverService" /> <constructor-arg name="persistRightOperandResolver" ref="persistRightOperandResolver" /> <constructor-arg name="logger" ref="tenantTechnicalLoggerService" /> </bean>
- Download the Bonita BPM community server archive file BonitaBPMCommunity-7.9.0.zip via the link received in your e-mail, get the file org.talend.mdm.bonita.server-A.B.C.jar (A.B.C corresponds to the package version number) under the directory BonitaBPMCommunity-7.9.0.zip\server\webapps\bonita\WEB-INF\lib and put it to the directory <Bonita_Home>\server\webapps\bonita\WEB-INF\lib.
-
Update the file custom-permissions-mapping.properties under the directory
<Bonita_Home>\setup\platform_conf\initial\tenant_template_portal
by adding the following code:
profile|User=[read_mdm_context]
-
Update the file resources-permissions-mapping.properties under the directory
<Bonita_Home>\setup\platform_conf\initial\tenant_template_portal
by adding the following code:
GET|extension/mdmcontext=[read_mdm_context]
-
Enable two properties SECURITY_OPTS and
CATALINA_OPTS in the file
<Bonita_Home>\setup\tomcat-templates\setenv.bat and update
their values to:
rem Optional JAAS configuration. Usually used when delegating authentication to LDAP / Active Directory server set SECURITY_OPTS="-Djava.security.auth.login.config=%CATALINA_HOME%\conf\jaas-standard.cfg" rem Pass the JVM system properties to Tomcat JVM using CATALINA_OPTS variable set CATALINA_OPTS=%CATALINA_OPTS% %PLATFORM_SETUP% %H2_DATABASE_DIR% %DB_OPTS% %BDM_DB_OPTS% %ARJUNA_OPTS% %INCIDENT_LOG_DIR% %SECURITY_OPTS% -Dfile.encoding=UTF-8 -Xshare:auto -Xms1024m -Xmx1024m -XX:+HeapDumpOnOutOfMemoryError
-
Update the cp command in the
file
<Bonita_Home>\setup\setup.bat with the
following content:
"%JAVA_CMD%" -cp "%BASEDIR%;%CFG_FOLDER%;%INITIAL_CFG_FOLDER%;%LIB_FOLDER%\*" %JVM_OPTS% -Dh2.noconfirm -Dspring.profiles.active=default -Dsysprop.bonita.db.vendor=%BONITA_DATABASE% org.bonitasoft.platform.setup.PlatformSetupApplication %otherArgs%
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!