Modify the installation in interactive mode

Modify the deployment of Connections by adding or removing applications.

Use the Modify function of the Installation Manager to add or remove Connections applications.

To modify the installation:

1. cd IM_root directory.

2. Run:

   • AIX or Linux: ./launcher

   • Windows: launcher.exe

3. From the Installation Manager menu, click File > Preferences.

4. Click Repositories.

5. In the Repositories area, select the repositories to modify.

6. Click OK to save the selections.

7. Click Modify.

8. Select IBM Connections, and click Next.

9. In the Application Selection page, choose the applications to add or remove and then click Next.

   • Add applications: Select the check boxes of any applications that are not already installed and to add to the deployment.

   • Remove applications: Clear the check boxes of any installed applications to remove from the deployment.

   • All installed applications are selected by default.

   • The Home page, News, and Search applications are required and cannot be removed.

10. Enter the administrative ID and password of the dmgr.

    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. To use security management software such as Tivoli Access Manager or SiteMinder, the ID specified here must exist in the LDAP directory. See Switch to unique administrator IDs for system level communication.

11. Configure your topology:

    • 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 we select an existing cluster on which to deploy applications, the nodes in that cluster are fixed and cannot be modified.

    • Small deployment:

      1. Select the Small deployment topology.

      2. Enter a Cluster name for the topology.

      3. Select a Node.

      4. Click Next.

    • Medium deployment:

      1. Select the Medium deployment topology.

      2. 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.

         Installation Manager creates servers and clusters when required.

      3. Select a Node for each cluster. Accept the predefined node or select a different node.

         These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

         The name must be unique across all nodes in the deployment.

      5. Click Next.

    • Large deployment:

      1. Select the Large deployment topology.

      2. Enter a Cluster name for each application.

         Installation Manager creates servers and clusters when required.

      3. Select a Node for each cluster. Accept the predefined node or select a different node.

         These nodes host application server instances that serve Connections applications. We can assign multiple nodes to a cluster, where each node is a server member of that cluster.

      4. Enter a Server member name for the selected node.

         The name must be unique across all nodes in the deployment.

      5. Click Next.

12. Enter the database information.

    The panel described in this step appears only if you selected new applications to install and if the new applications require database configuration.

    The IBM Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet deployment.

    Database information for Global Configuration Data and Object Store must be set correctly or installation will fail.

    1. Specify whether the installed applications use the same database server or instance: Select Yes or No.

       If allowed by the database configuration, we can select multiple database instances as well as different database servers.

    2. Select a Database type from one of the following options:

       • IBM DB2 Universal Database™

       • Oracle Enterprise Edition

       • Microsoft SQL Server Enterprise Edition

    3. Enter the Database server host name. For example: appserver.enterprise.myco.com

       If the installed applications use different database servers, enter the database host name for each application.

    4. Enter the Port number of the database server. The default values are: 50000 for DB2 , 1521 for Oracle, and 1433 for SQL Server.

       If wer installed applications use different database servers or instances, enter the port number for each database server or instance.

    5. 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

    6. Ensure the following JDBC driver libraries are present in the JDBC directory:

       DB2

       db2jcc4.jar and db2jcc_license_cu.jar

       Ensure the 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.

    7. 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.

       If the database type is Oracle, we must connect to the database with the user ID used when we created the application database.

    8. Click Validate to verify the database settings. If the validation fails, check the database settings. When the validation succeeds, click Next.

       Installation Manager tests the database connection with the database values that you supplied. We can change the database configuration later in the WAS console.

       Usually we can continue even if the validation failed because we can change the database settings from WAS console afterwards. However, we cannot continue if you have entered incorrect information for the Connections Content Manager database, because there are database operations during installation. Incorrect database information will cause installation to fail. So use correct information for Connections Content Manager database.

13. In the summary panel, confirm the selection and click Modify.

14. When the modification process is complete, restart the dmgr and all the nodes.

    Wait until the dmgr 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 the dmgr has distributed the application EAR files to the nodes, check SystemOut.log of each node agent. The default path to SystemOut.log 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 a Connections application.

    To confirm the installation was successful, open the log files in the connections_root/logs directory. Each Connections application that you installed has a log file, using the following naming format: application_nameInstall.log, where application_name is the name of a Connections application. Search for the words error or exception to check whether any errors or exceptions occurred during installation.

Results

Installation Manager writes the result of the installation command to the log file 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 Installation Manager records the values entered when we ran Installation Manager in interactive mode. To review the log file for 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...

• 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 Connections application that you installed has a log file, using the following naming format: applicationInstallog.txt, where application is the name of a Connections application.

Parent topic:
Install Connections

Related:

Configure media galleries

Related:

Switch to unique administrator IDs for system level communication