Scribd
Upload
278 views8 pages

Install JDK & Configure JBoss for MDM

Install the Java Development Kit (JDK) and set the JAVA_HOME and PATH environment variables. Install and configure JBoss with the standalone configuration and full profile. Configure JBoss properties, JAVA_OPTS, JGroups bind address, and JVM heap size. Disable remoting-connector security if logging into the Hub Console remotely.

Uploaded by

Laukik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
278 views8 pages

Install JDK & Configure JBoss for MDM

Install the Java Development Kit (JDK) and set the JAVA_HOME and PATH environment variables. Install and configure JBoss with the standalone configuration and full profile. Configure JBoss properties, JAVA_OPTS, JGroups bind address, and JVM heap size. Disable remoting-connector security if logging into the Hub Console remotely.

Uploaded by

Laukik
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Install Java Development Kit

If you are installing the Informatica MDM Hub on AIX, install a supported version of Java Development Kit
(JDK).
http://tecadmin.net/steps-to-install-java-on-centos-5-6-or-rhel-5-6/#

Set Environment Variables


Set the environment variables before you install the MDM Hub.
You must set JAVA_HOME and PATH environment variables to point to JDK 1.7.0_25 or later.

Install and Configure JBoss


Install and configure JBoss according to the instructions in the JBoss documentation. Ensure that you install
the
standalone configuration. Use the full profile of the standalone configuration. You can configure the full
profile in the
standalone-full.xml file.
Note: Install the application server in the same time zone as the database server.
Ensure that you perform the following configurations:
Add -Djava.net.preferIPv4Stack=true when you set up JBoss specific properties, JAVA_OPTS in the following
file
if the operating system uses Internet Protocol version 6 (IPv6):
On UNIX. <JBoss_install_dir>/jboss-eap-6.1/bin/standalone.conf.sh
On Windows. <JBoss_install_dir>\jboss-eap-6.1\bin\standalone.conf.bat
The following sample shows the setting:
# Set up JBoss specific properties
JAVA_OPTS="-Dprogram.name=$PROGNAME -Djava.net.preferIPv4Stack=true $JAVA_OPTS"
Add the following JVM option to the JBoss startup script to force JBoss and JGroups to use the same bind
address:
-Djgroups.bind_addr=<bind_addr>
In the sample, <bind_addr> specifies the interface on which to receive and send messages.
Set the maximum JVM heap size (-Xmx) to 4 GB or higher in the JBoss startup script. Change the following
settings:
set JAVA_OPTS=%JAVA_OPTS% -server -Xmx4096m -XX:PermSize=256m -XX:MaxPermSize=1024m
The -Xmx parameter must be three to four times the size of XX:MaxPermSize and -XX:PermSize must

$JBOSS_HOME
<JBoss_install_dir>/jboss-eap-6.1/bin/standalone.conf.sh
/usr/lib/jboss-eap-6.1/bin/ standalone.conf

Disable Remoting-Connector Security

If you need to log into the Hub Console from a remote machine, disable the remoting-connector security.
1. Open the following file in a text editor:
On UNIX.
<Jboss_install_dir>/jboss-eap-6.1/standalone/configuration/standalone-full.xml
On Windows.
<Jboss_install_dir>\jboss-eap-6.1\standalone\configuration\standalone-full.xml
2. Remove the security-realm attribute from the following code:
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector" socket-binding="remoting" securityrealm="
ApplicationRealm"/>

You might also like