Preload notice database support

Several database tables are created to store history about user access to preload notices. The information includes when a preload notice was last viewed, and the total number of times a preload notice has been viewed.

Before you begin

In a "config split" environment, in which database domains are shared between separate portal instances on a single server or on a WebSphere® Portal cluster, preload notice data is stored in a centrally located Customization database. Make sure that the Customization database is properly defined (with URL, user name, and password) in the wpconfig_dbdomain.properties file. For more information, refer to the WebSphere Portal product documentation.

About this task

User access history is used with defined preload notice rules to determine whether the preload notice will appear when a user clicks on a link configured with a preload notice.

User access history is cleared when a preload notice is deleted, or when the page, URL, or portlet containing the preload notice is deleted.

To clear user access history manually, follow this procedure:

CAUTION:

The WebSphere Portal server will be stopped when the procedure is performed.

Procedure

Change your working directory to wp_profile_root/ConfigEngine.
Run the following command:
```
./ConfigEngine.sh init action-mwp-create-pln-database-tables
```
```
ConfigEngine init action-mwp-create-pln-database-tables
```
Note: For security reasons, if you do not want to store the WebSphere Portal admin password and WebSphere Application Server admin password in the wkplc.properties file, you can specify the passwords on the portal server command line. For example, when this topic directs you to enter the ConfigEngine script or batch file, you would add parameters to the command to specify the password values as shown here:
```
./ConfigEngine.sh init task_name -DPortalAdminPwd=WP_admin_password_value -DWasPassword=WAS_admin_password_value
```
```
ConfigEngine init task_name -DPortalAdminPwd=WP_admin_password_value -DWasPassword=WAS_admin_password_value
```
Note: All of this text, including parameters, is entered on the same command line.
where:
- task_name is the name of the configuration task being invoked (for example, mcs-deploy-mcs)
- WP_admin_password_value is the value of the WebSphere Portal admin password
- WAS_admin_password_value is the value of the WebSphere Application Server admin password if WebSphere Application Server security is enabled
Attention: Special considerations apply if you are using a Microsoft SQL Server database. For information about installing WebSphere Portal Server with Microsoft SQL Server, contact your IBM Support representative.
Verify that there are no errors in the output.
Note: The results of the create preload database tables task are displayed on the screen and logged to the wp_profile_root/ConfigEngine/log/ConfigTrace.log file. If errors occur during the creation, correct the problems and rerun the create preload database tables task.

Restart the portal server using the following commands:

wp_profile_root/bin/stopServer.sh server_name -username WAS_admin -password WAS_admin_password_value

wp_profile_root/bin/startServer.sh server_name

wp_profile_root\bin\stopServer server_name -username WAS_admin -password WAS_admin_password_value

wp_profile_root\bin\startServer server_name

where server_name is the name of the WebSphere Application Server instance (for example, WebSphere_Portal).