When you have met all of the prerequisites noted in the previous sections, you are ready to run the Database Loader and WebSphere Partner Gateway installation wizards. These wizards can be executed directly, or through the LaunchPad. See, LaunchPad for more information.
http://www-1.ibm.com/servers/aix/products/aixos/linux/download.html
The Database Loader and Hub install wizards use the X Windows system on UNIX to display the graphical user interface. The X Windows system requires that the DISPLAY environment variable be exported to the system environment. The following lines set the DISPLAY environment variable to the IP_Address from a Bourne shell:
DISPLAY=IP_Address:0.0
export DISPLAY
Use the syntax appropriate to your shell to set the DISPLAY environment variable.
WebSphere Partner Gateway provides a LaunchPad program to provide one-stop access to the Product Overview, ReadMe File, product documentation, Database Loader, and WebSphere Partner Gateway Installer. Alternatively, you can start the database loader and installation programs using the supplied setup*.* programs. See, Creating the database, and Installing the components using the install wizard.
The LaunchPad executable file is located in:
{CD_ROM/MEDIA DIR}/LaunchPad.sh
WebSphere Partner Gateway includes an installation wizard to set up the database tables. This wizard, Database Loader, gathers information to create and populate the tables for you. Alternatively, it can save the SQL files it uses to create the tables. You can then use the SQL files to create and populate the tables. Running the SQL files manually allows you to review the database tables before populating them.
Before you begin, verify that your database server is installed, configured correctly, and running.
DBLoader can be run on a machine that does not have the actual database. Oracle/DB2 should be installed on that machine, but the actual database can be on another machine. The DBA needs to do some configuration changes for that, which probably are out of scope of this guide. First you create the database on a remote machine. Then you configure a remote database with oracle/db2 on the machine on which dbloader will be installed, specifying on which machine its running , which port it uses etc. Once this configuration is done, DBLoader can be run as if the database is local. The Oracle/DB2 will automatically take care of the rest. All sql commands against this database will goto the correct machine for processing. The SQLs can be run automatically.
The following procedure describes how to configure the database using the Database Loader GUI. You can also install the Database Loader without using the GUI. See Installing the components using the command line for information.
To set up the database tables:
Database Loader requires administrator privileges to automatically run the SQL create/change ownership of the tablespaces directories.
cd DBLoader
Platform | Executable |
---|---|
Linux |
setupLinux |
AIX |
setupAIX |
Solaris |
setupSunOS |
The Database Loader wizard starts and displays the Welcome window. Click Next.
Select a location with enough space for your database and all the application data that will be stored in it. Click Next.
DB2:
If you selected DB2, the DB2 Database Information window appears. Enter the following DB2 database information:
Oracle:
Once you have entered the required information, click Next.
DB2
Oracle
In the User name and Password fields for the Community Console, Document Manager, and Receiver, type the name and password of the user for each component. If using DB2, these users were created when the server was configured.
In the Group Name field, type the name of the group that contains the WebSphere Partner Gateway users.
When the Database Loader runs the SQL files, it does the following:
Because the Database Loader restarts the DB2 instance as part of its routine, disconnect any applications that are using the DB2 instance where you are setting up the WebSphere Partner Gateway database.
If you want the Database Loader to run the files for you, select the Run the SQL files check box. Click Next.
When you have set up the WebSphere Partner Gateway database, you are ready to install the WebSphere Partner Gateway components.
The following section describes how to install the components using the InstallShield wizard GUI. You can also install the components without using the GUI. See Installing the components using the command line for information.
WebSphere Partner Gateway has three main components: Community Console, Receiver, and Document Manager. All three components share common content. You can install the components and common content on a single server, install each component on a separate server, or use a combination of these two options. You must install one instance of each component on at least one server. See Environment planning and Topologies for information on how to plan the placement of the various components on different servers.
Before you begin, make sure that the prerequisite software is installed and configured properly. Consult the Requirements for all WebSphere Partner Gateway servers table in Platform, hardware, and software requirements for software prerequisites and Installation overview for information on how to configure that software. You must also have the WebSphere Partner Gateway database set up. For information on this, see Creating the database. Finally, your database server and WebSphere MQ must be running, including the queue manager and listener.
Common components need to be installed only once when using anything other than the consolidated topology.
To install WebSphere Partner Gateway:
The Hub installer requires root/Administrator privilege to integrate with the native software registry.
Platform | Executable |
---|---|
Linux |
setupLinux |
AIX |
setupAIX |
Solaris |
setupSolaris |
The wizard starts and displays the Welcome window. Click Next.
The rest of this procedure assumes that you are installing all of the components. If you are not installing all of them, some of the windows described in the rest of this procedure will not appear.
If you select this option, another window will appear and you must enter the directory where WebSphere Application Server is installed.
DB2
If you selected DB2, the DB2 Database information window appears. Figure 10.
Enter the Host name of the computer running DB2 if it is not installed on the current system by replacing localhost with the name of the system containing DB2.
In the Port field, type the port number that the DB2 instance is using. To find out which port the DB2 instance is using either use the DB2 Control Center (GUI) to determine the properties or enter the following DB2 configuration command on a command prompt: db2 get dbm cfg. This DB2 configuration information is also saved by the Database Loader in the system temp/bcgdbloader/logs directory. The default port is 50000.
In the Owner name, Owner password, Database name, and Schema name fields, type the owner name, owner's password, database name and the instance name respectively. These are the names used in the Database Loader installation to define the database. See Creating the database.
Click Next.
Oracle:
If you selected Oracle, the database information window appears, see Figure 11.
Enter the required information about the Oracle database. The default port is 1521.
The full path and name of the JDBC driver must point to the correct version of the driver on this computer. The driver can be found in the Oracle installation directory.
It can also be downloaded from http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html. In the section JDBC Driver Downloads, click on Oracle xx Release x drivers. Be sure to select the driver version that matches the Oracle xx version that you are running.
Click Next.
The database connection confirmation window will appear. See Figure 12. If your connection is successful, note and confirm the Table, View, Function, and Procedure count information. If the connection fails, review the information window for guidance, or refer to your database documentation to address the error code.
In the Host name field, if WebSphere MQ is not on the current machine, replace localhost with the name of the system containing WebSphere MQ.
In the Queue Manager field, replace the default name with the name that was used when configuring WebSphere MQ (See step 2 in Configuring WebSphere MQ).
In the Listener Port field, type the port that the listener is using (see Configuring WebSphere MQ). The default port is 9999.
Click Next.
In the User name field, type the user ID that the Community Console component uses to log in to the database.
In the Password field, type the password associated with the user name. Make sure that you enter the correct password because the Community Console will not function with an incorrect password.
In the HTTP port field, type the name of the port on which the component listens for messages. The Community Console, Receiver, and Document Manager must have unique port numbers, and they must be available on this computer. The default port is 58080.
In the HTTPS port field, type the name of the secure port on which the component listens for messages. The Community Console, Receiver, and Document Manager must have unique port numbers, and they must be available on this computer. The default port is 58443.
Click Next.
In the Name field, type the name of the person that should be contacted for RosettaNet problems.
In the Phone number and Fax number fields, type the telephone and fax numbers for the RosettaNet contact.
In the e-mail address field, type the e-mail address for the RosettaNet contact person.
Click Next.
In the SMTP relay field, type the host name of the SMTP if it is not running on this computer.
In the From e-mail address field, type the e-mail address, that WebSphere Partner Gateway will use to send e-mails.
In the To e-mail address field, type the destination e-mail address that users responding to alert notifications use when they send a response e-mail.
Click Next.
Repeat this procedure on each server where you want to install WebSphere Partner Gateway components. The common content needs to be installed only once because it is available to all computers via the shared file system.
When you have installed all WebSphere Partner Gateway components, see Starting WebSphere Partner Gateway.