Installation Guide for IBM Db2 with Red Hat JBoss

10.4 HotFix 1

Back Next

Configuring EJB Security

You can configure EJB security at the JBoss application server level or at the Hub Server level to prevent unauthorized access to data and other resources in the

MDM Hub

. To configure EJB security at the JBoss application server level, enable the JBoss remoting-connector security.

Ensure that the password that you set adheres to the JBoss password policy and the configured MDM Hub global password policy. This is important because the same password needs to be set for the Hub Console and for JBoss.

For information about the MDM Hub global password policy, see the

Multidomain MDM Configuration Guide

Disable remoting-connector security.

Change the Hub Console password to adhere to the JBoss password policy.

Connect

Select the

Users

tool under

Configuration

workbenches and acquire a write lock.

Select the

admin

user under the

User

tab, and click the

Change password

icon.

The

Change Password

dialog box appears.

Change the password to adhere to the JBoss password policy, and click

Enable the remoting-connector security in the

standalone-full.xml

file.

Open the

standalone-full.xml

file in the following directory:

JBoss installation directory

>/standalone/configuration

Add the

security-realm

attribute as shown in the following code:

In the subsystem with the name

urn:jboss:domain:remoting:<n.n>

, add the following attribute to the

remoting-connector

configuration:

security-realm=<"<security realm name>">

In JBoss, register the

MDM Hub

users that must have access to the Hub Server.

Run the following script to register the

MDM Hub

users:

On UNIX.

JBoss installation directory

>/bin/add-user.sh

On Windows.

JBoss installation directory

>\bin\add-user.bat

Answer the prompts in the following table:

Prompt	Value
What type of user do you wish to add? a) Management User (mgmt-users.properties) b) Application User (application-users.properties)	Specify the option b .
Realm (ApplicationRealm)	Use the name of the security realm. Default is ApplicationRealm .
Username	User name of the MDM Hub user.
Password	Password of the MDM Hub user that adheres to JBoss password policy.
What roles do you want this user to belong to?	You must specify hubconsole .

Enable JBoss security on the Hub Server.

Open

cmxserver.properties

in the following directory:

MDM Hub installation directory

>/hub/server/resources

Uncomment the following property:

#cmx.jboss7.security.enabled=true

Repackage the Hub Server EAR files.

Navigate to the following directory:

MDM Hub installation directory

>/hub/server/bin

Run the following command:

On UNIX.

./sip_ant.sh repackage

On Windows.

sip_ant.bat repackage

Deploy the Hub Server EAR files.

Stop the JBoss application server.

If you have any existing deployments, remove the following deployment files from the JBoss deployment directory:

Deployment File Name	Description
siperian-mrm.ear	Required. The Hub Server application.
provisioning-ear.ear	Required. The Provisioning tool application.
entity360view-ear.ear	Optional. The Entity 360 framework.
informatica-mdm-platform-ear.ear	Optional. The Informatica platform application.
ave_jboss.ear	Required. The ActiveVOS Server application.
activevos-central.war	Required. The ActiveVOS Central application.