The name of the LikeMinds Personalization Server server to install in WebSphere Application
Server.
JDBCProviderName
The name to assign to the JDBC provider to create in the LikeMinds Personalization Server
DbType
The type of database to use. This must be one of:
db2
db2_iseries_toolbox
db2_iseries_native
oracle
JDBCDriver
The fully qualified path of the JDBC driver.
Note:
Windows users must use forward slashes '/' to denote path structures, instead of backslashes
'\'.
If you have used the default quick install of WebSphere Commerce, the JDBC provider will be
called, "demo - WebSphere Commerce JDBC Provider".
DatasourceName
The name to assign to the datasource.
DataBaseName
The name of the LikeMinds database.
DataBaseUser
The ID to use to connect to the LikeMinds database.
DataBasePassword
The password associated with the ID.
EARPath
The fully qualified path to the LikeMinds utility EAR.
Note: Windows users must use forward
slashes '/' to denote path structures, instead of backslashes '\'.
DataBaseServer
The name of the server on which the database resides.
DataBasePort
The port number used during database creation. If a port number was not used during database
creation, a port number of 50000 should be used if the DbType is db2 or 1521
should be used if the DbType is oracle.
Note: If you encounter "cmdline buffer overflow" errors, copy the PZN_Utilities.ear file to a
folder higher in the tree, such as /usr/PZN_Utilities.ear. Alternatively, define a variable for
"/WebSphere/CommerceServer70", and use the variable in place of the full directory path. The goal is
to reduce the string required to identify the path, which will correct the error.