Identity Suite v15 deployment using JBoss EAP 8.0 RPM multi-instance pattern
Article ID: 443253
Updated On:
Products
Issue/Introduction
This article describes the supported approach for deploying CA Identity Suite r15 components (Identity Manager, Identity Portal, and Identity Governance) on a Linux server where JBoss EAP 8.0 Update 12 has already been installed using the RPM installation method.
The article also confirms support for using the JBoss multi-instance pattern, where multiple Identity Suite components share a common JBoss installation (JBOSS_HOME) while maintaining separate instance-specific configurations (JBOSS_BASE_DIR).
Environment
Identity Governance and Administration (IGA) 15.0 and higher
IGA Xpress 1.0 and higher
Cause
Existing JBoss Installation
JBoss EAP 8.0 Update 12 installed via RPM package:
JBOSS_HOME=/opt/jboss
The RPM installation provides the JBoss binaries and runtime under:
/opt/jboss
Proposed Architecture
Identity Manager Instance
Create a dedicated JBoss base directory for Identity Manager:
JBOSS_HOME=/opt/jboss
JBOSS_BASE_DIR=/var/opt/ca/idm/standalone
Copy the existing standalone configuration:
cp -R /opt/jboss/standalone /var/opt/ca/idm/
Result:
/opt/jboss (Shared JBoss binaries)
/var/opt/ca/idm/standalone (Identity Manager instance)
Identity Portal Instance
JBOSS_HOME=/opt/jboss
JBOSS_BASE_DIR=/var/opt/ca/portal/standalone
Identity Governance Instance
JBOSS_HOME=/opt/jboss
JBOSS_BASE_DIR=/var/opt/ca/ig/standalone
Resolution
Question 1
Can Identity Manager be installed using this architecture?
Answer: Yes.
The described approach follows the standard JBoss multi-instance deployment pattern and is supported for Identity Suite v15 deployments.
In this model:
- A single JBoss installation is shared through JBOSS_HOME.
- Each Identity Suite component uses its own dedicated JBOSS_BASE_DIR.
- Configuration files, deployments, logs, temporary files, and runtime data remain isolated per instance.
Example:
JBOSS_HOME=/opt/jboss
Identity Manager:
JBOSS_BASE_DIR=/var/opt/ca/idm/standalone
This provides operational isolation while minimizing storage and maintenance requirements by sharing a single JBoss binary installation.
Question 2
Can the same procedure be reused for Identity Portal and Identity Governance?
Answer: Yes.
The same multi-instance approach can be used for:
- Identity Manager
- Identity Portal
- Identity Governance
Example layout:
/opt/jboss
/var/opt/ca/idm/standalone
/var/opt/ca/portal/standalone
/var/opt/ca/ig/standalone
Each component maintains:
- Its own configuration files
- Its own deployments
- Its own logs
- Its own temporary directories
- Its own runtime state
while sharing the common JBoss EAP installation.
This architecture is similar to the deployment model used by the Identity Suite Virtual Appliance.
Additional Information
To ensure a successful setup, please follow these guidelines:
Java Version: Verify that your environment is running Java 17 or higher, as required for JBoss 8.0 support.
Instance Isolation: Ensure that each instance has its own unique set of ports (if running on the same IP) to avoid socket binding conflicts.
Permissions: Ensure the service user has full read/write permissions to the JBOSS_BASE_DIR paths and read/execute permissions for the JBOSS_HOME path.
Feedback
