Modify your deployment of IBM® Connections
by adding or removing applications.
About this task
Use the Modify function of the IBM Installation
Manager to add or remove IBM Connections
applications.To
modify your installation, complete the following steps:
Procedure
- Open a command prompt and change to the IM_root directory.
- Run the following command:
- AIX or Linux: ./launcher
- Windows: launcher.exe
- From the IBM Installation
Manager menu, click .
- Click Repositories.
- In the Repositories area, select the repositories that
you want to modify.
- Click OK to save your selections.
- Click Modify.
- Select IBM Connections
and click Next.
- In the Application Selection page, choose the applications
you want to add or remove and then click Next.
- Add applications: Select the check boxes of any applications
that are not already installed and that you want to add to your deployment.
- Remove applications: Clear the check boxes of any installed
applications that you want to remove from your deployment.
Notes:
- All installed applications are selected by default.
- The Home page, News, and Search applications are required and
cannot be removed.
-
Enter the administrative ID and password of the Deployment Manager.
Note: This ID is set to
the connectionsAdmin J2C authentication alias,
which is mapped to the following Java™ EE
roles: dsx-admin, widget-admin,
and search-admin. It is also used by the service
integration bus. If you plan to use security management software such
as Tivoli® Access Manager
or SiteMinder, the ID that you specify here must exist in the LDAP
directory. For more information, see the Switching to unique
administrator IDs for system level communication topic.
- Configure
your topology:
Notes:
- The panel described in this step appears only if you selected
new applications to install.
- The applications for Connections Content Manager will not be shown
if you have chosen to use an existing FileNet® deployment.
- If you select an existing cluster on which to deploy applications,
the nodes in that cluster are fixed and cannot be modified.
- Small deployment:
- Select the Small deployment topology.
- Enter a Cluster name for the topology.
- Select a Node.
- Click Next.
- Medium deployment:
- Select the Medium deployment topology.
- Select the default
value or enter a Cluster name for each application
or for groups of applications. For example, use Cluster1 for Activities,
Communities, and Forums.
Note: IBM Installation Manager creates servers and
clusters when required.
- Select a Node for
each cluster. Accept the predefined node or select a different node.
Note: These nodes host
application server instances that serve IBM Connections
applications. You can assign multiple nodes to a cluster, where each
node is a server member of that cluster.
- Enter a Server
member name for the selected node. Choose the default
or enter a custom name.
Note: If you enter a custom server member name,
the name must be unique across all nodes in your deployment.
- Click Next.
- Large deployment:
- Select the Large deployment topology.
- Enter a Cluster
name for each application.
Note: IBM Installation Manager creates servers and
clusters when required.
- Select a Node for
each cluster. Accept the predefined node or select a different node.
Note: These nodes host
application server instances that serve IBM Connections
applications. You can assign multiple nodes to a cluster, where each
node is a server member of that cluster.
- Enter a Server
member name for the selected node. Choose the default
or enter a custom name.
Note: If you enter a custom server member name,
the name must be unique across all nodes in your deployment.
- Click Next.
-
Enter the database information.
Note: The panel described
in this step appears only if you selected new applications to install
and if the new applications require database configuration.
Note: The IBM Connections Content Manager
databases will not be shown if you have chosen to use an existing FileNet deployment.
Note: Database
information for Global Configuration Data and Object Store must be
set correctly or installation will fail.
- Specify whether the installed applications use the same
database server or instance: Select Yes or No.
Note: If allowed by your database configuration, you can select
multiple database instances as well as different database servers.
- Select
a Database type from one of the following options:
- IBM DB2 Universal Database™
- Oracle 12c Enterprise
- Microsoft SQL Server Enterprise
Edition
- Enter
the Database server host name. For example: appserver.enterprise.example.com
If your installed applications use different database servers,
enter the database host name for each application.
- Enter
the Port number of the database server. The
default values are: 50000 for DB2®, 1521 for Oracle,
and 1433 for SQL Server.
If your
installed applications use different database servers or instances,
enter the port number for each database server or instance.
- Enter
the JDBC driver location. For example:
- AIX:
/usr/IBM/WebSphere/AppServer/lib
- Linux:
/opt/IBM/WebSphere/AppServer/lib
- Windows:
C:\IBM\WebSphere\AppServer\lib
- Ensure
that the following JDBC driver libraries are present in the JDBC directory:
- DB2
- db2jcc4.jar and db2jcc_license_cu.jar
Note: Ensure
that your user account has the necessary permissions to access the DB2 JDBC files.
- Oracle
- ojdbc6.jar
- SQL Server
- Download the SQL Server JDBC 4 driver from the Microsoft website to a local directory
and enter that directory name in the JDBC driver library field.
The
directory must not contain the sqljdbc.jar file,
only the sqljdbc4.jar file. Even though the data
source is configured to use the sqljdbc4.jar file,
an exception occurs if both files are present in the same directory.
- Enter the User ID and Password for
each database.
If each database uses the same user credentials,
select the
Use the same password for all applications check
box and then enter the user ID and password for the first database
in the list.
Note: If
your database type is Oracle, you must connect to the database with
the user ID that you used when you created the application database.
- Click Validate to verify your
database settings. If the validation fails, check your database settings.
When the validation succeeds, click Next.
IBM Installation Manager tests your
database connection with the database values that you supplied. You
can change the database configuration later in the WebSphere® Application Server Integrated
Solutions Console.
Note: Usually you can continue even if the validation failed because you can change the database
settings from WebSphere Application Server Integrated
Solutions Console afterward. However, you cannot continue if you entered incorrect information for
the IBM Connections Content Manager database because there are
database operations during installation. Incorrect database information causes installation to fail.
So you must use correct information for IBM Connections
Content Manager database.
- In the summary panel, confirm your selection and click Modify.
- When the modification process is complete, restart the
Deployment Manager and all the nodes.
Note: Wait until the
DM copies all the application EAR files to the
installedApps directory
on each of the nodes. This process can take up to 30 minutes.
To
verify that the DM has distributed the application EAR files to the
nodes, check the SystemOut.log file of each node
agent. The default path to the SystemOut.log file
on a node is profile_root/logs/nodeagent.
Look
for a message such as the following example: ADMA7021I: Distribution
of application application_name completed successfully. where application_name is
the name of an IBM Connections
application.
To confirm that
the installation was successful, open the log files in the connections_root/logs directory.
Each IBM Connections application
that you installed has a log file, using the following naming format: application_nameInstall.log,
where application_name is the name of an IBM Connections application. Search
for the words error or exception to
check whether any errors or exceptions occurred during installation.
Results
IBM Installation Manager writes
the result of the installation command to the log file that you specified
with the -log parameter.
If the installation
is successful, the log files are empty. For example:
<?xml version="1.0" encoding="UTF-8"?>
<result>
</result>
The log file contains an error element if
the operation was not completed successfully. A successful installation
adds a value of 0 to the log file. An unsuccessful installation adds
a positive integer to the log file.
The
log file for IBM Installation
Manager records the values that you entered when you ran IBM Installation Manager in interactive mode.
To review the log file for IBM Installation
Manager, open the
date_time.xml file,
where
date_time represents the date and time of
the installation. The file by default is in the following directory:
- AIX or Linux (root user): /var/ibm/InstallationManager/logs
- AIX or Linux (non-root user): user_home/var/ibm/InstallationManager/logs where user_home is
the non-root user account directory
To check the complete details of the installation, open each
of the log files in the
connections_root/logs directory.
Each IBM Connections application
that you installed has a log file, using the following naming format:
applicationInstallog.txt,
where
application is the name of an IBM Connections application.