Working with Database Security
The libraries and tables delivered by the Platform Pack installation are not secured. In order to provide sufficient security, you should run the tool SETOWAUT which allows you to 'lock down' libraries and IFS directories delivered by the Platform Pack installation. You can obtain the latest version of the SETOWAUT tool from the Update Center using the Change Assistant.
In order to maximize your database security, you should change the passwords on all table owners created during the Platform Pack installation; these are created with the user and password equal to the same value. Such a user and password relationship could expose you to worms and viruses aimed at gaining access to your database. Consult with your DBA for advice on changing passwords to meet the security requirements of your database installation.
The Installation Workbench assumes that the database user is JDE and that the password is
the same, unless it finds this override in the jde.ini file on the
Deployment Server. Once the database passwords have been changed, you will need to add
this section to the jde.ini file:
[DSPWD] JDE=new_password
For example, if you changed the password for JDE to alaska5, your
section would look like this:
[DSPWD] JDE=alaska5
After you change the [DSPWD] section of the jde.ini file, logon to OneWorld in the JDEPLAN environment on the Deployment Server with the new password in the correct case.
jde.ini file match that of your database. For applicable
instructions, refer to the chapter entitled: Chapter 10, "Performing Post Upgrade
Tasks" in the section entitled: Chapter 10.1, "Working With Signon Security and
Table Creation Security". You should secure the jde.ini file on the Deployment Server to
prevent unauthorized access. You should delete the [DSPWD] section once the install or upgrade is
complete.