This appendix contains the following topics:
Before you build a package, you must have a security administrator add a security override if your system meets both of these conditions:
The database that you are using is Oracle, SQL, or IBM DB2 for LUW (Linux, UNIX, Windows).
The security server is enabled.
A security override is required so that the package build process can create the metadata repository tables in central objects. To add a security override, a security administrator must first add a system user for the central objects data source owner, and then add a security override for the JD Edwards EnterpriseOne user who will run the package build.
To add a system user for the central objects data source owner:
In JD Edwards EnterpriseOne Solution Explorer, enter P98OWSEC in the Fast Path.
On Work with User Security, from the Form menu, select Add System User.
On Work with System Users, in the System User field, enter the appropriate data source owner, for example DV900, PY900, or PD900.
Click the Find button.
If no values are returned, add the data source owner as a system user:
Click the Add button.
On System User Revisions, complete these fields: System User, Data Source, Password, and Password Verify.
Click OK and then click the Cancel button.
Click the Close button to return to the Work with User Security form.
To add a security override to run package build:
On Work with User Security, enter the user who is going to run the package build, and then click the Find button.
From the Form menu, select Add Data Source.
On Add Data Source, complete these fields:
User ID
Data Source
System User
Note:
For iSeries, either sign in as a user who has rights to create tables in the central objects library, or follow the steps to set up a security override for the JD Edwards EnterpriseOne user. When the JD Edwards EnterpriseOne user connects to the data source, the user connects as a system user (iSeries user profile) who has update rights to the library.