Post installation tasks for the server

This section provides information about tasks you need to complete after you install DB2 Everyplace on a server. The topics covered are:

Creating a DB2 Everyplace instance on UNIX

If you did not create a DB2 Everyplace instance during installation or you would like to create additional instances outside of the installation process, use the dsyicreate.sh command.

Note:
A DB2 Everyplace instance must be a DB2 Universal Database instance as well. Therefore, only user IDs which are DB2 instance owners can host a DB2 Everyplace instance.

Procedure

To create a DB2 Everyplace Sync Server instance, use the dsyicreate.sh command located in the instance directory of the root installation directory (/opt/DB2Everyplace81 on Linux and Solais and /usr/lpp/DBEveryplace81 on AIX ). Execute the dsyicreate.sh command as root user.

You will receive a list of parameters that you need to provide in order to create a DB2 Everyplace Sync Server Instance. These parameters are specific to the setup type that you selected during the DB2 Everyplace installation.

Related tasks

Mapping a source database to a mid-tier server

Procedure

If your source database exists on a different workstation than the mid-tier server, link to the source database from the DB2 Universal Database Control Center. In the Control Center, you must add the host system, create an instance for the host system, and if necessary, add the database to the host system using an alias for the name of the mid-tier database.You can create the mid-tier database from a DB2 Universal Database command line (use the command: db2 create db), or use the Database Create wizard in the DB2 Universal Database Control Center. To create a mid-tier database on your local machine and on the Sync Server instance, both the mid-tier database and the Sync Server control database (DSYCTLDB) must use the same code page.

Related tasks

Enabling replication

Procedure

To replicate between the mirroring server and DB2 Universal databases, you must create a table subscription for your databases. Replication is set up automatically when you install the Sync Server. For Data Propagator subscriptions, replication must be run on the server hosting the mirror database.

For detailed information about propagating data, see the DB2 Universal Database Replication Guide and Reference.

Related tasks

Setting up sample databases and applications

If you did not choose to create the sample databases during installation, you can install them at any time.

The DB2 Everyplace Sync Server samples and sample database configuration include:

Procedure

To install the sample on a Windows operating system

  1. Open a DB2 UDB command Window, change the directory to %DSYINSTDIR%\Server\Sample.
  2. Type dsysample.bat and the user name and password. Execute the command.

To install the sample on a UNIX operating system

  1. Login as the DB2 Everyplace instance owner
  2. Open a shell window and change the directory to $DSYINSTDIR/Server/sample
  3. Run dsysample.sh db2userid db2password where db2userid is a valid DB2 Universal Database user ID, and db2password is the corresponding password.

Related tasks

Testing the Sync Server servlet

To ensure that the Sync Server can successfully communicate with clients, you should check the servlet. You do not need to have any clients installed in order to perform a check.

Procedure

You should receive the following message for both Windows and UNIX: 

DB2e SyncServer <datetime string>

For the Application Server - Express that ships with DB2 Everyplace, you might receive a message in the server log files located in [DSYINSTDIR]/Server/logs/[servername] that port is already taken by another program. If you receive this message, change the port number.

The embedded Application Server - Express has been changed between DB2 Everyplace 8.1.2 and 8.1.4. The default value during installation for Server name is IBMDB2eServer. The default value during installation for the server IP address is 127.0.0.1.

To change the port number:

  1. Windows: 
    cd [DSYINSTDIR]\Server\installableApps\common
[DSYINSTDIR]\WAS\bin\stopServer.bat DB2eServer
[DSYINSTDIR]\WAS\bin\wsadmin.bat -conntype NONE -f dsyConfigEmbedded.jacl
DefaultNode default_host DB2eServer 127.0.0.1 [DSYINSTDIR] [new http port] [new https port]
  2. Linux or UNIX: 
    cd [DSYINSTDIR]/Server/installableApps/common
[DSYINSTDIR]/WAS/bin/stopServer.sh DB2eServer
[DSYINSTDIR]/WAS/bin/wsadmin.sh -conntype NONE -f dsyConfigEmbedded.jacl
DefaultNode default_host DB2eServer 127.0.0.1 [DSYINSTDIR] [new http port] [new https port]

Related tasks

Configuring Sync Server to use with IBM WebSphere Application Server

This section describes how to configure the DB2 Everyplace Sync Server so you can use it with the IBM WebSphere Application Server 4.0 Advanced Edition and Advanced Single Server edition. The following topics are covered in this section:

Prerequisites

Before you start, make sure that you have WebSphere Application Server 4.0, FixPak 2 or higher installed on your workstation. You can download the FixPak from the IBM Web site. You will also need the following information:

The WebSphere Application Server Administration Server must use the default port number 900. If not, configure the WebSphere Application Server Administration Server to use 900 now. After you finish configuring the Sync Server, you can change it back.

For Windows 2000, Windows NT, and Windows XP, if you are using DB2 UDB Version 7, you must first configure WebSphere Application Server to use JDBC 2.0. To configure WebSphere Application Server to use JDBC 2.0:

  1. Stop the DB2 Universal Database JDBC Applet Server service.
  2. Stop WebSphere Application Server if it is running.
  3. Open a Command Prompt window.
  4. Change the directory to %DSYSQLLIBINSTDIR%\java12.
  5. Type usejdbc2.bat. If errors messages appear, you need to verify that the DB2 Universal Database JDBC Applet Server service has stopped.
  6. Start the DB2 Universal Database JDBC Applet Server service.
  7. Start the WebSphere Application Server.

You must also have the DB2 Universal Database administrator's authority for Windows NT, Windows 2000, or Windows XP operating systems; or the root user authority for the UNIX operating system.

Procedure

To configure Sync Server to use with WAS 4.0 Advanced Edition

  1. Start the IBM HTTP Server.
  2. Start the Administration Server for WAS 4.0.

    When you start the Administration Server, you must log in as a DB2 Universal Database administrator on a Windows NT, Windows 2000, or Windows XP operating system, or as root user on the UNIX operating system. The administration server must use the default port number 900 now, but you can change the server to use another port at a later time.

  3. Run the dsy_was40_install script. This script will create an application server under your WebSphere node, install the IBM DB2 Everyplace Enterprise Application, and regenerate the Web server plug-in. To start the script:

To configure Sync Server to use with WAS 4.0 Advanced Single Server Edition

This section describes how to configure Sync so you can use it with WAS 4.0 Advanced Single Server Edition. There are two parts to configuring the Sync Server so you can use it with WAS 4.0 Advanced Single Server Edition. You need to update the classpath for the default application server and install the IBM_DB2_Everyplace.ear file on the WebSphere Application Server.

To update the classpath for the IBM DB2 Everyplace Server

  1. In the WebSphere Administration Domain tree, expand the components Nodes -> Node name -> Application Server -> IBM DB2 Everyplace Server -> Process Definition -> JVM Settings. The JVM Settings page opens.
  2. In the Properties panel, type a classpath for the default application server and click OK.
  3. In the JVM Settings page, click the Configuration needs to be saved link.
  4. Click OK to save the configuration.
  5. Stop the WebSphere Application Server.
  6. Restart the WebSphere Application Server. When the WebSphere Application Server is restarted, the new JVM classpath is effective.
  7. Restart the WebSphere Application Server Administrative Console.

Related tasks

Configuring and Installing DB2 Everyplace with WebSphere Application Server Version 5.0

This section describes how to configure and install DB2 Everyplace as a server application which runs in the WebSphere environment. The topics covered are:

Configuring and Installing DB2 Everyplace with WebSphere Application Server Version 5.0

Installing DB2 Everyplace into WebSphere Application Server (WAS) provides a robust runtime environment for DB2 Everyplace and other applications. DB2 Everyplace is shipped with the Embedded Version of the WebSphere Application Server Version 5. If full support for a J2EE environment is desired for DB2 Everyplace and your own applications, WebSphere Application Server is recommended.

This section describes how to configure and install DB2 Everyplace as a server application which runs in the WebSphere environment. These instructions are applicable to WAS Version 5.0. This topic includes:

Related concepts

Gathering configuration information

Procedure

This topic lists the information that you need to gather and provide during various configuration tasks.

Related concepts

Related tasks

The WAS installation scripts

DB2 Everyplace provides three scripts to help you install DB2 Everyplace into WAS:

A forth script is available to uninstall DB2 Everyplace from WAS (dysUnInstallDB2e.jacl). The script files are all executed from within the following directory, <DB2 Everyplace installation root>/Server/installableApps/common. We recommend that you use the command line environment with these scripts for most of your installation and administrative needs. In a few cases, we refer you to the WAS Administrative Console.

Related tasks

Installation and configuration overview

Procedure

The main tasks involved in setting up your system to work with WAS Version 5.0 are as follows:

Related concepts

Related tasks

Creating and installing an application server

The DB2 Everyplace application server is created by the following steps, with the appropriate configuration parameters. If a copy of the DB2 Everyplace server is already running, stop the server before continuing.

Prerequisites

For UNIX environments, complete the following tasks:

Procedure

To create the server, type:

Related concepts

Related tasks

Creating a cluster environment

Procedure

For cluster environments:

Creating DB2 Everyplace in a cluster environment involves three steps:

Related concepts

Related tasks

Adding the server nodes

Procedure

To add the server nodes:

  1. Open the Administrative Console.
  2. From the Navigation Tree, click System Administration --> Nodes.
  3. In the Workspace, click Add Node to add the server nodes that will be in the cluster. Use the fully qualified name to specify each node to be added in the host field. If the node is not found, make sure that server1 is started on each node, which services the configuration request from the WAS Deployment Manager.

    The Node Agent will be started for the node, and the node will be added to a network named <hostnameNetwork> Network. Once you add the nodes, you can create the cluster.

Related concepts

Related tasks

Creating the cluster

Procedure

To create a DB2 Everyplace cluster, use the dsyCreateCluster.jacl script:

After execution, a new cluster with the name "DB2Everyplace_Cluster" is created.

Related concepts

Related tasks

Adding new servers to the cluster

Procedure

To add a new clusterMember to the cluster created above:

  1. Refer to the instructions in the Enabling replication.
  2. Issue the following commands:
Note:
Please refer to the DB2 Everyplace Installation topics for important information regarding cluster environments.

Related concepts

Related tasks

Administrative tasks

There are three administrative task that you can perform:

Related concepts

Related tasks

Uninstalling DB2 Everyplace from WAS

Procedure

To uninstall the DB2 Everyplace application, issue the following command:

The Virtual Host may still have the ports associated with the removed DB2 Everyplace application server db2everyplaceapplication after that application server has been uninstalled. These remaining ports can be safely removed.

Related concepts

Related tasks

Starting and stopping the DB2 Everyplace application server

There are two ways you can start and stop the DB2 Everyplace server. You can use the command prompt. If you are running in a Network Deployment environment, it is recommended that you use the Administrative Console.

Prerequisites

Before you issue the commands, you must set the DISPLAY environment variable in the shell in which the command to start the server is issued. For example, export DISPLAY=:0.0.

Procedure

To start and stop the DB2 Everyplace application server using the command prompt, enter the following commands:

The server name is an exact string match of the server that was created. The stopServer command stops the server.

In cluster environments, starting and stopping, or otherwise manipulating the created cluster is simplest in the Administrative Console. To start and stop a cluster, go to <your network> --> Servers --> Clusters. Select the cluster by clicking the check box to the left of the cluster name, and then click Start or Stop.

If the console lists a cluster member as unavailable, make sure the node agent is started on the node, and the node configuration is synchronized with the deployment manager configuration. The node synchronization status can be viewed under System Administration -> Nodes.

Related concepts

Related tasks

Deleting the Cluster

Procedure

To delete the cluster:

  1. Open the Administrative Console.
  2. Stop and remove the DB2 Everyplace enterprise application by navigating to <your network> Applications --> Enterprise Applications.
  3. Click the check box to the left of the application server name. Stop any running server that is a cluster member of the DB2 Everyplace cluster by clicking Stop servers.
  4. Remove the stopped DB2 Everyplace cluster by navigating to <your network>Servers --> Clusters. Select the check box to the left of the server cluster name and click Delete.

Related concepts

Related tasks

Regenerating the Web Server plugin

The WebSphere plugin configuration file provides configuration information to redirect requests to the appropriate application server running in WebSphere.

Procedure

To update the web server plugin configuration for DB2 Everyplace, issue the following command:

After generating the new plugin configuration file, you may have to copy the file elsewhere depending on the location of your web server. If the front end HTTP Servers are located on separate severs (other than where WAS is installed), be sure to copy it to the correct server where it was configured. The generated plugin configuration file is usually located in <was_home>/config/cells/plugin-cfg.xml. If you are running a WebSphere Network Deployment configuration, the plugin file is located in the network deployment directory as [ND home]/config/cells/plugin-cfg.xml.

Note:
You can also regenerate the plugin in the Administrative Console. Navagate to <your network>Environment --> Update Web Server Plugin. Click OK.

Related concepts

Related tasks

Configuring a multiple server environment

This section provides information about configuring a multiple server environment. The topics covered are:

Configuring a multiple server environment

In a multiple server environment, DB2 Everyplace exploits WebSphere Application Server (WAS) technology to dynamically manage user loads across servers by distributing the load between different servers. Incoming work requests are distributed to the application server and other objects that can most effectively process that request. WAS implements workload management by using server groups and clones.

Prerequisites

You must have the following software installed in order to use a multiple server environment:

Procedure

  1. Set up to create application server clones.
  2. Create application server clones.
  3. Complete post-configuration tasks.

Related concepts

Server groups and clones

A server group contains a template of an application server (and it's contents). It is based upon a server that you have set up and it is used for creating and managing copies of that server. The copies are called clones. The act of creating the clones is called cloning.

Cloning is an advanced technique for improving the performance and availability of an application server. Cloning allows the workload management system to transparently balance the application server workload among the clones in the server group and automatically switches users from failed application instances to active clones with no interruption in service. The transparency of cloning to the user makes cloning an invaluable technique for maintaining a highly efficient and reliable production environment.

The server group is a logical representation of the application server. It has the same structure and attributes as the real application server, but it is not associated with any nodes, and does not correspond to any real server process running on any node. In contrast, clones created from a server group represent real application server processes running on real nodes.

Clones are identical to the server group from which they are created, allowing identical application servers to be created. These copies can be used for workload management, since a request for a server resource can be handled by any of the server clones. Staring or stopping the server group will automatically start or stop the server clone. Changes to a server group will be propagated to its clones when the server group is restarted.

Related concepts

Related tasks

Planning considerations and tips

In order to exploit the benefits of load balancing in a server group, it is important to consider how to set up this complex environment. You should consider:

Related concepts

Related tasks

Setting up to create application server clones

This topic describes some setup tasks you must perform before you can create server clones from your server group.

This task is part of the main task of Configuring a multiple server environment. After you complete these steps, return to Configuring a multiple server environment.

Procedure

  1. Ensure that all servers in your server group have a static IP address with a fully qualified host name.
  2. Install DB2 Universal Database, Version 7.2.1:
    1. Install DB2 Universal Database, Version 7.2.1 on each physical server.
    2. After rebooting the server, install FixPak 5. Where possible, accept the defaults.
    3. Stop all DB2 services.

      If you are using a Windows NT workstation, switch the JDBC level to 2.0. Change the usejdbc2.bat file in the \Program Files\java12 directory.

    4. Restart the DB2 services.
  3. Install WebSphere Application Server, Version 4.0 with FixPak 2 and FixPak 3.
  4. Install IBM DB2 Everyplace on each physical server. Select the Multiple Server Environment installation type.
  5. Repeat steps 1- 5 for each additional physical server in your server group.
  6. Choose a WAS server and Install the IBM_DB2_Everyplace.ear file into the WAS server that you selected.
    1. Run the scripts:
      • If the WAS server is on a UNIX platform, run the scripts in ${DSYINSTDIR}/Server/installableApps/unix

        dsy_was40_install.sh "$(WebSphere Application Server installation home)" adminnodename "$DSYINSTDIR" "$DSYQLLIBINSTDIR"

      • If the WAS server is on a Windows platform, run the scripts in %DSYINSTDIR%\Server\installableApps\nt

        dsy_was40_install.bat "WebSphere Application Server installation home" adminnodename "%DSYINSTDIR%" "%DSYQLLIBINSTDIR%"

      This command creates an Application Server on the DB2 Everyplace Server, installs the DB2 Everyplace EAR file, regenerates the plug-in configuration that the servlet redirector uses to route requests, and starts the DB2 Everyplace Sync Server.

    2. Verify the installation of the DB2 Everyplace EAR file by opening a Web browser. Type http://hostname/db2e/db2erdb. If the server running a message will be returned with the servlet name and other relevant information.

Related concepts

Related tasks

Creating application server clones

This section contains a high-level description of how to create server groups and clones.

Note:
If you are using your server for replication purposes only, it is recommended that you do not add your clones into the DB2 Everyplace Server Group. The synchronization requests might be sent to the replication server, which will not reply to the client.

This task is part of the main task of Configuring a multiple server environment. After you complete these steps, return to Configuring a multiple server environment.

Prerequisites

Before you create application server clones, you must complete some setup tasks as described in Setting up to create application server clones.

Procedure

To create application server clones:

  1. Stop the application server that you want to clone.
    1. Open the WebSphere Administrative Console, and go to WebSphere Administrative Domain --> Node --> domain name --> Application Servers --> IBM DB2 Everyplace Application Server.
    2. Right-click the application server and select stop.
  2. Create a new server group by right-clicking on the application server and select Create Server Group. In the Create Server Group window, type a name for the new server group (for example, DB2 Everyplace Server Group). Click OK.

    A server group is created, and the original application server is now a clone in the server group.

  3. Copy the expanded EAR files to the other application servers when prompted by the Administrative Console.
  4. Right-click each node, and select Regenerate Plugin Config so that the system will recognize each clone.
  5. Select one node, and copy the $WAS_HOME/config/plugin-cfg.xml file to your front-end IBM HTTP Server.
  6. Specify a different server port for each clone.
    1. Select Nodes --> nodename--> Application server clone name.
    2. In the right plane, go to Services and select Web Container. Click Edit.
    3. Click the Transport tab on the properties window and note the port number.
    4. Go to System Properties in the right pane, and type the name value pair: DSYGdflt.Server.Port, transport_port_number for the application server clone.
    5. Restart the server if it was already running.

      If the topology for your multiple server environment has vertical scaling, you must also define a unique value for each of the servers on the same server for the property:

      • DSYGdflt.Trace.Path = log_directory
      • DSYGdflt.Server.Name = UniqueName (type a unique name without spaces)
  7. If you are using virtual hosts to support different Web groups, you need to add the same port number to the list of virtual hosts.
    1. Select WebSphere Administrative Domain -> Virtual Hosts
    2. In the right pane, click add and type the port number that you obtained previously.
    3. Click Apply.
  8. Right-click each node, and select Regenerate Plugin Config so that the system will recognize each clone.
  9. Select one node, and copy the $WAS_HOME/config/plugin-cfg.xml file to your front-end IBM HTTP Server.

After you complete these tasks, you can start the multiple server environment.

To start the multiple server environment, right-click on the new server group and select start. All clones that belong to that server group should start, and the front-end HTTP server with the servlet redirector will begin to receive all the requests.

Related concepts

Related tasks

Post-configuration tasks

This topic contains post configuration tasks that will help you manage a multiple server environment.

This task is part of the main task of Configuring a multiple server environment. After you complete these steps, return to Configuring a multiple server environment.

Procedure

Related concepts

Related tasks