Modifying the installation in console mode

Using console mode, modify your deployment of IBM® Connections by adding or removing applications.

1. On each node, stop any running instances of WebSphere® Application Server and WebSphere node agents.
2. Start WebSphere Application Server Network Deployment Manager. On IBM i, you need to run Installation Manager from Qshell. To do so, run the QSH or STRQSH command to start a Qshell session first.
3. Open a command prompt and change to the IM_root/eclipse/tools directory.
4. Run the following command to start IBM Installation Manager in console mode:
   • AIX or Linux: ./imcl -c
   • IBM i: imcl -c
   • Windows: imcl.exe -c
5. Type 3 to begin modifying the deployment.
6. In the Select packages to modify step, select IBM Connections and then type N to proceed.
7. Select the applications that you want to add or remove and then type N.
   • Add applications: Type the numbers corresponding to applications that are not already installed and that you want to add to your deployment.
   • Remove applications: Type the numbers corresponding to installed applications that you want to remove from your deployment. The Home page, News, and Search applications are required and can't be removed.
   Notes:

   • All installed applications are selected by default.
8. 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.
9. Configure your topology. For more information about each option, refer to Deployment options.
   Note: If you chose to use existing deployment of FileNet for Connections Content Manager, the application Connections Content Manager will not show in this topology panel.
   • Small deployment:
     1. Type 1 to select the Small deployment topology.
     2. Enter a Cluster name for the topology.
     3. Select a Node.
     4. Enter a Server member name for the node.
     5. Type N to proceed.
   • Medium deployment:
     1. Type 2 to 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.
        Note: IBM Installation Manager creates servers and clusters when required.
     3. 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.
     4. 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.
     5. The topology that you specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
     6. Type N to proceed.
   • Large deployment:
     1. Type 3 to select the Large deployment topology.
     2. Enter a Cluster name for each application.
        Note: IBM Installation Manager creates servers and clusters when required.
     3. 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.
     4. 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.
     5. The topology that you specified is displayed. To re-specify any details, type the number that corresponds to the application; for example, type 1 for Activities.
     6. Type N to proceed.
10. Note: Database information for Global Configuration Data and Object Store must be set correctly; otherwise, installation will fail.
    Enter the database information:
    Attention: The Connections Content Manager databases will not be shown if you have chosen to use an existing FileNet deployment.
    Note: For IBM i, IBM Connections Content Manager for the Libraries only supports an existing FileNet deployment on AIX or Linux
    1. Specify whether the installed applications use the same database server or instance: Type 1 to specify that the applications use same database server or instance; type 2 to specify that they use different database servers or instances.
       Note: If allowed by your database configuration, you can select multiple database instances as well as different database servers.
       Note: IBM Connections on IBM i uses the same installation code framework with other platforms, and there are some Database terminologies for other platforms that do not apply to IBM i, so you can just ignore them and keep with the default values. You can consider a database instance as a DB2 for IBM i server. If you select to install Metrics, make sure you select 2 because the Metrics database needs to be DB2 on AIX.
    2. Select a Database type from one of the following options: If installing on Windows, Linux, or AIX:
       • IBM DB2 Universal Database™
       • Oracle Enterprise Edition
       • Microsoft SQL Server Enterprise Edition

       If installing Connections on IBM i, you only can choose DB2 UDB for IBM i as the Database type. If you select to install Metrics, to simplify the Database configuration, with DB2 UDB for IBM i selected, the installer will automatically convert the Metrics Database type to db2 internally.

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

    4. Enter the Port number of the database server. The default values are: 50000 for DB2(r)®, 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.

       Note: Database Name and Port number do not apply to DB2 for IBM i, so you can just ignore them and keep with the default values. For Metrics, since the Metrics database is DB2 on AIX, you need to provide the Database name and port number to make the Installer configure them correctly.
    5. Enter the JDBC driver location. For example:
       • AIX:

         /usr/IBM/WebSphere/AppServer/lib

       • IBM i: /QIBM/ProdData/HTTP/Public/jt400/lib

         For Metrics on IBM i, the Metrics database uses the DB2 LUW JCC JDBC driver, which can be copied from the java directory of the DB2 installation on LUW. The db2jcc4.jar and the db2jcc_license_cu.jar need to be copied to an IBM i IFS directory. By default, IBM Installation Manager checks the /QIBM/ProdData/DB2LUW/JdbcDriver directory for these JDBC driver files.

         Note: To use the DB2 LUW JCC JDBC driver, you need to have a 64-bit JRE 60 of at least SR 15, Fix Pack 1, or a 64-bit JDK 626 of at least SR 7, Fix Pack 1.
       • Linux:

         /opt/IBM/WebSphere/AppServer/lib

       • Windows:

         C:\IBM\WebSphere\Appserver\lib

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

       DB2 UDB for IBM i

       jt400.jar

       If you select Metrics, make sure you also have the following JDBC driver: db2jcc4.jar and db2jcc_license_cu.jar.

    7. Enter the User ID and Password for each database. If each database uses the same user credentials, confirm the Use the same password for all applications question 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.

    8. If you need to make changes, type the number that corresponds to the application that you want to change. Alternatively, type R to reset all the database specifications to their default values.
    9. Press Enter 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 afterwards. However, you cannot continue if you have entered incorrect information for the IBM Connections Content Manager database, because there are database operations during installation. Incorrect database information will cause installation to fail. So you must use correct information for IBM Connections Content Manager database.
11. Review the information that you have entered. To revise your selections, press B. To finish modifying, press M.
12. Review the result of the installation. Press F to exit the installation wizard.
13. Restart the Deployment Manager:
    • AIX(r) or Linux(tm): Open a command prompt and change to the app_server_root/profiles/Dmgr01/bin directory. Enter the ./stopManager.sh command and then enter the ./startManager.sh command.
    • IBM i: Run the STRQSH or the QSH command to start a Qshell session, then change to the profile_root/dmgr/bin directory. Enter the stopmanager dmgr -username AdminUserId -password AdminPwd command and then enter the startmanager dmgr command.
    • Windows(tm): Stop and restart the Deployment Manager service.
14. Start all the federated nodes and enter the startNode command. Repeat these steps for each node:
    1. Log in to a node.
    2. From a command line, change to the profile_root/bin directory.
    3. Enter the startNode command for your operating system:
       • AIX or Linux: ./startNode.sh
       • IBM i: startNode
       • Windows: startNode.bat
15. Log in to the Integrated Solutions Console on the DM to perform a full synchronization of all nodes.
    1. Go to System administration > Nodes.
    2. Select the nodes and click Full Resynchronize.
    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.

16. Start all your IBM Connections clusters:
    1. Log in to the Integrated Solutions Console on the DM.
    2. Navigate to Servers > Clusters > WebSphere Application server clusters.
    3. Select the IBM Connections clusters and click Start.
    Note: If some applications do not start, the file-copying process might not have completed. Wait a few minutes and start the applications. In case the Connections applications are installed on different clusters, the cluster start order should be as follows:

    • Profiles cluster
    • Communities cluster
    • News cluster
    • Search cluster
    • Dogear cluster
    • Activities cluster
    • Blogs cluster
    • Files cluster
    • Forums cluster
    • Wikis cluster
    • Hompage cluster
    • Metrics cluster
    • Mobile cluster
    • Moderation cluster
    • Connections Content Manager cluster
      Note: The Connections Content Manager cluster will not be listed in the Integrated Solutions Console when you are setting up Connections Content Manager with an existing FileNet® deployment; that is, with a FileNet deployment that was not implemented through the Connections installer. In this case, the FileNet components would show in the Integrated Solutions Console associated with it.