Deploying and Configuring with JBoss | ||
---|---|---|
Previous | Next | |
Deploying and Configuring with Apache Tomcat | Deploying and Configuring with GlassFish |
This section explains how to configure and deploy the Semarchy Convergence for MDM Application with JBoss Application Server.
In this section,
<jboss_home>
refers to the JBoss server installation folder.
Note: Refer to the JBoss Documentation for your JBoss version for more details about the deployment and configuration processes in JBoss.
The JBoss 5 web service native stack is not supported by Semarchy. It needs to be replaced by JBossWS-CXF.
To install CXF:
temp
folder.
jbossws-cxf-bin-dist
sub-directory, save the
ant.properties.example
file as
ant.properties
.
jboss510.home
,
jbossws.integration.target
,
jboss.server.instance
,
jboss.bind.address
according to your JBoss configuration. For example:
jboss510.home=<jboss_home>
jbossws.integration.target=jboss510
jbossws-cxf-bin-dist
directory, install JBossWS-CXF by running the ANT build script:
ant deploy-jboss510
This version of JBoss is configured by default to delete the application working directory when the server is restarted. This behavior is similar to redeploying the original application at server startup. With this behavior, plug-ins added to the Semarchy application disappear when the server restarts.
To prevent this effect, the JBoss 6 configuration needs to be changed.
To configure work directory deletion to false:
<jboss_home>/server/configuration/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml
file.
<property name="deleteWorkDirOnContextDestroy">false</property>
To install the Oracle JDBC driver for JBoss 5 and 6:
ojdbc6.jar
) in the
<jboss_home>/server/configuration/lib
directory.
To install the Oracle JDBC driver for JBoss 7:
ojdbc6.jar
) in the
<jboss_home>/standalone/deployments
directory.
Warning: The configuration in this section uses the UsersRolesLoginModule (properties file based login module) and may be changed to a stronger authentication mechanism.
To configure the security realm for JBoss 5 and 6:
<jboss_home>/server/configuration/conf/props/semarchy-users.properties
file with the following user and password definition:
semadmin=<semadmin_password>
<jboss_home>/server/configuration/conf/props/semarchy-roles.properties
file with the following user/role mapping:
semadmin=semarchyConnect,semarchyAdmin
<jboss_home>/server/configuration/conf/login-config.xml
and add the section given below.
<!-- Sample configuration for the semarchy realm. -->
<application-policy name="SemarchyRealm">
<authentication>
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
flag="required">
<module-option
name="usersProperties">props/semarchy-users.properties</module-option>
<module-option
name="rolesProperties">props/semarchy-roles.properties</module-option>
</login-module>
</authentication>
</application-policy>
To configure the security realm for JBoss 7:
<jboss_home>/standalone/configuration/semarchy-users.properties
file with the following user and password definition:
semadmin=<semadmin_password>
<jboss_home>/standalone/configuration/semarchy-roles.properties
file with the following user/role mapping:
semadmin=semarchyConnect,semarchyAdmin
<jboss_home>/standalone/configuration/standalone.xml
and add the section given below in the
<subsystem xmlns="urn:jboss:domain:security:1.0"><security-domains>
configuration element .
<!-- Sample configuration for the semarchy application. -->
<security-domain name="SemarchyRealm" cache-type="default">
<authentication>
<login-module code="UsersRoles" flag="required">
<module-option name="usersProperties"
value="<jboss_home>/standalone/configuration/semarchy-users.properties"/>
<module-option name="rolesProperties"
value="<jboss_home>/standalone/configuration/semarchy-roles.properties"/>
</login-module>
</authentication>
</security-domain>
To configure the repository datasource:
<jboss_home>/server/configuration/deploy/semarchy_repository.xml
file based on the template given below. Make sure to modify the
connection-url
,
user-name
and
password
elements to match your repository schema connection information.
<datasources>
<no-tx-datasource>
<jndi-name>jdbc/SEMARCHY_REPOSITORY</jndi-name>
<connection-url>jdbc:oracle:thin:<oracle_instance_hostname>:<oracle_listener_port>@<oracle_service_name></connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name><repository_user_name></user-name>
<password><repository_user_password></password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
</no-tx-datasource>
</datasources>
Important: Do not change the jndi-name of the SEMARCHY_REPOSITORY datasource. The application refers to a datasource with this name for the repository.
To configure a data location datasource:
<jboss_home>/server/configuration/deploy/
an XML file named after the data location, and based on the template given below. Make sure to modify the
jndi-name
,
connection-url
,
user-name
and
password
elements to match your data location schema connection information:
<datasources>
<no-tx-datasource>
<jndi-name>jdbc/<data_location_datasource_name></jndi-name>
<connection-url>jdbc:oracle:thin:<oracle_instance_hostname>:<oracle_listener_port>@<oracle_service_name></connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name><data_location_user_name></user-name>
<password><data_location_user_password></password>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
</no-tx-datasource>
</datasources>
Repeat this operation for each data location’s datasource.
The repository and data location datasources are now configured, pointing to the schemas previously created.
To configure the repository datasource:
SEMARCHY_REPOSITORY
jdbc/SEMARCHY_REPOSITORY
<repository_user_name>
<repository_user_password>
jdbc:oracle:thin:
@
<oracle_instance_hostname>:<oracle_listener_port>:<oracle_service_name>
To configure a data location datasource:
<data_location_datasource_name>
jdbc/<data_location_datasource_name>
<data_location_user_name>
<data_location_user_password>
jdbc:oracle:thin:
@
<oracle_instance_hostname>:<oracle_listener_port>:<oracle_service_name>
The repository and data location datasources are now configured, pointing to the schemas previously created.
To deploy the application for JBoss 5 and 6:
semarchy_war_only.zip
file in the
temp/
folder.
temp/semarchy.war
file in the
<jboss_home>/server/configuration/deploy/
folder.
To deploy the application for JBoss 7:
semarchy_war_only.zip
file in the
temp/
folder.
temp/semarchy.war
file in the
<jboss_home>/standalone/deployments/
folder.
The Semarchy application is deployed in the server.
This configuration is required for mail notifications using JEE Mail Session.
To configure JavaMail Session for JBoss 5 and 6:
<jboss_home>/server/<configuration>/deploy/mail-service.xml
and alter the default service configuration for your network. See http://community.jboss.org/wiki/JavaMail for more information.
To test the application:
http:/<jboss_host>:<jboss_port>/semarchy/
.
Tip: Proceed directly to the Installing the Repository task.
Previous | Top | Next |
Deploying and Configuring with Apache Tomcat | Deploying and Configuring with GlassFish |