The default installation location for the Content Manager OnDemand for Multiplatforms server and Content Manager OnDemand Web Enablement Kit (ODWEK) have changed. In addition, the installers also allow for the default installation directory to be changed. This also effects other components of the OnDemand Server like ACIF User Exits and the DB2 Log User Exit. There is also a new command, arsstash, for managing encrypted userid passwords for automated access to Content Manager OnDemand.
The installation directory location is important to note because changing the directory location affects upgrade instructions. In version 9.0 and previous releases, the installer removes the previous version of Content Manager OnDemand prior to installing version 9.0. The new installer does not change the directory location where the installation occurs, but it does include the version number being installed. As with all installations of Content Manager OnDemand, refer to the installation Readme files for any additional installation and configuration instructions.
New default Installation directory locations:
|Operating system||OnDemand server installation directory||ODWEK installation directory|
|AIX, HP-UX, Solaris||/opt/IBM/ondemand/V9.0||/opt/IBM/odwek/V9.0|
|Linux (both x64 and System z)||/opt/ibm/ondemand/V9.0||/opt/ibm/odwek/V9.0|
|Windows||C:\Program Files\IBM\OnDemand for Windows\V9.0||C:\Program Files\IBM\OnDemand Web Enablement Kit\V9.0|
It is possible that you might have used scripts or other ways (for example, cron) to invoke the Content Manager OnDemand commands. If so, you should identify those areas so that they are configured to use the correct installation directory.
If you choose to install in a different directory than the default, you must add the new install lib64 path to the library search path using the environment variables LIBPATH for AIX or LD_LIBRARY_PATH for the other UNIX platforms.
For Content Manager OnDemand for Windows, the OnDemand Configurator migrates all instances defined to use the new installation path.
For Content Manager OnDemand for UNIX, ensure that all configuration files (for example, ars.ini and ars.cfg) are correct and reference the correct paths.
For the Content Manager OnDemand Web Enablement Kit, the CGI and Servlet only support the default installation location. The default installation location should not be modified. If you use the Java APIs and you install to a non-default location, in your application you must use the following:
Properties props = new Properties();
ACIF User Exits
Remember: It is always good practice to recompile any custom user exit when installing a new version.
The apka2e and asciinpe default user exits utilize codepage conversion from ICU. The conversion tables for ICU are a part of the Content Manager OnDemand installation directory. The exits can leverage the correct installation directory. However, if your user exit was created to also use ICU, it needs to be evaluated or modified to reflect the new ICU location. Sample code is provided as part of apka2e.c and asciinpe.c in the ACIF exits installation directory.
In the Content Manager OnDemand application definition, it is possible to specify the indexing parameters including user exits. All user exits must be specified with an absolute path. If the arsload command determines that a pre-V9.0 installation location for the exit is specified, but the exit no longer exists in that location, the path is modified with the new installation location.
arsload automatically changes this location to be
To modify your installation location:
Where $(OD_ACIF_EXIT_DIR) is replaced with the correct installation directory. For example, the AIX installation directory would be:
Use the listed convention to allow for easier upgrades in the future and is platform neutral which makes changing the loading platform easier. You can use arsload on Windows or UNIX without having to modify the application parameters.
This is true for all user exit definitions (not just INPEXIT)
When the arsdb –cv command was initially used to create the Content Manager OnDemand instance, it was possible that a default db2 user exit was placed (linked) for use by DB2 to either place archive logs into either TSM or a filesystem. This exit is called db2uext2.
The arsdb -cv command would create a link called db2uext in the DB2 userid home directory. For example, if the DB2 userid is ‘archive’, then ~archive/sqllib/bin/db2uext – would be a link to /usr/lpp/ars/config/db2uext2.disk on AIX. This is no longer the case with OnDemand V9, instead the arsdb -cv command will use native DB2 archive logging facilities.
It is recommended that customers no longer use the OD provided db2uext2 exit given that DB2 now has built in support for both archive disk/TSM logging, See the DB2 documentation describing the DB2 database configuration parameter LOGARCHMETH1
For instance - you can eliminate the use of the db2uext2 user exit and use native DB2 archive logging with the following:
db2 update database config for ARCHIVE using LOGARCHMETH1 DISK:/arsdb_archivelog/ARCHIVE
db2 update database config for ARCHIVE using LOGARCHMETH1 TSM
It should be noted that OnDemand (including the arsdb -y or -z command) does not manage and/or delete any DB2 archive logs.
In Content Manager OnDemand V9.0, a new concept has been introduced in order to remove all user IDs and passwords from being specified in either configuration files or directly to the command. The arsload.cfg file is no longer used, nor is the following values in the ars.cfg file: ARS_ORACLE_USERID, ARS_ORACLE_PASSWD, ARS_LDAP_BIND_DN, ARS_LDAP_BIND_DN_PWD.
The arsstash command has been introduced which allows customers to store encrypted user IDs and passwords to a file. See the Content Manager OnDemand Administration Guide for a description of this command.
To define a default stash file for an OnDemand instance you could place the stash file in the <install>/config directory. For instance, you could name the stash file ars.stash and then update the OnDemand instance definitions through the ars.ini file (on UNIX) to use that stash file.
If arssockd needs to use a userid/password for DB2, Oracle, LDAP – it uses the user ID and password specified in this file for those components.
The arsload, arsrdf, and arsdd commands could also use this file by specifying the OnDemand instance name and determine the default user ID and password. This method cannot be used with a hostname.
For all OnDemand commands that require a password, the default stash file for the instance is used. If you wish to override the default instance stash file, just specify the stash file name to the –p <stash_file> parameter instead of the actually password. For instance:
arsdoc query –I ARCHIVE –u oduser …
The arsdoc command uses the ARCHIVE instance stash file and the password stored for userid: oduser
arsdoc query –I ARCHIVE –u oduser –p ./ars.stash
The arsdoc command uses the password stored in ./ars.stash for userid: oduser
You should restrict access to any Content Manager OnDemand stash file by operating system permissions to just those that need to utilize the stash file. Otherwise, you are enabling others to be able to leverage the same Content Manager OnDemand user IDs and passwords (although they cannot see the password, they could run commands against Content Manager OnDemand as those users).