Prerequisites checklist

Ensure that the following prerequisites are met before attempting to install Intelligent Notification Services. Refer to the WebSphere Everyplace Access documentation to learn which versions of the prerequisite software is supported for this package.

	Ensure that the hardware requirements are met. Click here for a list of hardware requirements.
	Ensure that IBM Directory Server is installed and running. It can be running either locally or remotely.
	Ensure that IBM DB2 Universal Database is installed and running. The Intelligent Notification database or tables are created using either of these database servers. The database server can be running locally or remotely. If the database server is running remotely, you must have a database client running on the local machine. For DB2, the installer creates an Intelligent Notification database.
	Ensure that WebSphere Application Server and WebSphere Portal are installed and running. The WebSphere Application Server can be running locally or remotely.
	If you are going to use a remote database, ensure that the database has been created.
	If you are going to create a database or database tables locally during installation, ensure that the specified user has the rights to create a database or tables in the database. This is the user that you specify in the database panels of the Intelligent Notification installer.
	Preparing to use an existing IBM Directory Server: When installing with an existing WebSphere Portal, use the existing IBM Directory Server that is used by WebSphere Portal. In order to use this existing LDAP server, you must add an LDAP suffix and LDAP object for Intelligent Notification Services. Follow the directions below.

Preparing to use an existing IBM Directory Server: When installing with an existing IBM Directory Server, you must add an LDAP suffix and LDAP object for Intelligent Notification Services. Follow these steps to add the LDAP suffix and object.

1. Add a suffix to LDAP for Intelligent Notification Services.
   1. Go to the log-in URL for your IBM Directory Server, for example,

      http://server.location.company.com/ldap

      The IBM Directory Server log-in page appears.
   2. Enter your administrative user ID and password for LDAP, for example,

      cn=wpsadmin/wpadmin

      Select Logon.
   3. In the left-hand frame, click Settings then Suffixes. The suffixes panel appears on the right.
   4. Enter the suffix designation in the Suffix DN field, for example,

      dc=ins,dc=ibm,dc=com

2. Add an LDAP object and assign permissions for that object.
   1. Start the Directory Management Tool.
   2. Log in with your administrative user ID and password, for example,

      cn=wpsadmin/wpsadmin

   3. Select Directory tree then Browse tree.
   4. Select the Add button from the toolbar. The panel to add an LDAP entry appears.
   5. Select an entry type of Domain.
   6. Enter the suffix designation in the Entry RDN field, for example,

      dc=ins,dc=ibm,dc=com

   7. Click OK
   8. Highlight the suffix in the directory tree, for example,

      dc=ins,dc=ibm,dc=com

   9. Select ACL from the toolbar.
   10. Give Grant permissions everywhere possible on the screen.

Configuration parameters checklist

You must enter the following information during installation. You might want to prepare this information ahead of time.

Note: The installation does not necessarily follow the same order as the chart below.

Configuration parameter	Parameter value
Local machine
	Install directory (the location to which you want to install Intelligent Notification)
	Host name for the local machine (fully-qualified)
	SNMP host name (if you are going to enable SNMP) - optional
	SNMP port (if you are going to enable SNMP) - optional
	Directory where IBM Directory Server (LDAP) client is installed: IBM Directory Server client must be installed so that the Intelligent Notification install program can configure LDAP settings. This is only necessary if the IBM Directory Server is installed remotely from Intelligent Notification Services.
IBM Directory Server (LDAP)
	LDAP server host name (fully-qualified)
	LDAP server port
	Administrative user name
	Administrative password
	LDAP suffix: root node for the directory tree
	Has the LDAP server been initialized yet with Intelligent Notification settings? (Enter yes or no.)
	Realm (ou.realm)
Creating the Intelligent Notification database
	Will you be creating a new Intelligent Notification database or using an existing Intelligent Notification database? (Enter yes or no.)
	What type of database server are you using? (Enter DB2.)
	Database server host name (if using an existing database)
	database name
	database user name
	database user password
	database JDBC driver: name of the JDBC driver, for example, db2java.zip for DB2
WebSphere Portal These values are necessary for installing the Intelligent Notification portlets
	What version of WebSphere Portal are you using? (Enter 4.1 or 4.2x)
	WebSphere Portal host name (fully-qualified)
	Portal base URI (All URLs beginning with this path will be reserved for the portal.)
WebSphere Application Server
	WebSphere Application Server install directory
Administration Server
	Administration Server host name (fully-qualified)
Message Center portlet
	message size: maximum size for each stored message. The default is 8K.
	subject size: maximum size for the subject of each stored message. The default is 1K.
Trigger Manager
	Gryphon Broker host name
	Gryphon Broker port
	Universal Notification Dispatcher host name: This value is only necessary if you are performing a multiple-machine install.
Universal Notification Dispatcher
	Location and file name of the file where delayed notifications will be stored. For example, on Windows, C:/temp/undDelayQueue on Unix, /tmp/undDelayQueue
Secure Context Server
	User Privacy Manager host name: This value is only necessary if you are performing a multiple-machine install.
	User Privacy Manager port: This value is only necessary if you are performing a multiple-machine install.