Stage - 3 : Post-Setup

---

Running Database Scripts and Loading the MRL

The steps you take to run the database scripts and load the master resource library (MRL) vary, depending on the type of database you are using.

If you are using	Follow these steps
An Oracle database	Running the Oracle Database Scripts
A DB2 database	Running the DB2 Database Scripts
SQL Server database	Running the SQL Server Database Scripts

Note: To change the Studio user passwords from the Assembly Line schema password, update this script before running it by modifying the Insert commands for the DMRES_DMUSER table.

Running the Oracle Database Scripts

Follow these steps to run the Oracle database scripts:

1. Run the scripts located in the /documaker/database/oracle11g directory. You may need to copy these files to the database server. To run these files, you must have permission to create tables and insert data into the database. These scripts create the required Document Factory administrative and processing database tables. Contact your database administrator (DBA) for assistance.

   Script	Description
   dmrk_admin.sql	Creates the configuration schema and populates the tables with the entries captured during setup.
   dmkr_asline.sql	Creates the assembly line schema and the Documaker Studio default user accounts.

   Note: The scripts enable advanced compression on certain database columns. If you do not have an Advanced Compression Options license for Oracle 11g, please remove the COMPRESS DEDUPLICATE and COMPRESS HIGH DEDUPLICATE attributes from the scripts in dmkr_asline.sql.

2. To create sample user accounts for demonstration purposes and to test the deployment, run the following as the dmkr_admin user:

   dmkr_admin_user_examples.sql

3. (Optional) ODEE includes database entries that enable the ODEE web applications to be viewed in other languages. To add support for languages other than English, perform these steps:

   1. Make sure the script is executed using UTF-8 encoding so the Unicode text within the script is put into the database properly

      If you are using	Then
      SQL Developer to run the script	Change the file encoding option to UTF-8 by selecting the Tools, Preferences, Environment option and then setting the Encoding option to UTF8.
      SQL Plus to run the script	Set this environment variable (for Windows): NLS_LANG=AL32UTF8

   2. Run the following scripts as the dmkr_admin user:

      • dmkr_admin_xx.sql

      • dmkr_asline_xx.sql

      Where xx is the abbreviation for the desired language:

      Languages	Abbreviation
      Dutch	nl
      English (Great Britain)	en_GB
      French	fr
      German	de
      Indonesian	in
      Japanese	ja
      Polish	pl
      Portuguese	pt
      Russian	ru
      Simplified Chinese	zh
      Spanish	es

   3. Make sure the insert statements are committed to the database.

4. Run this script from the application server dmres directory to load the Correspondence MRL:

   ./deploysamplemrl.sh

   Typically, this script will be in the \documaker\mstrres\dmres\ directory.

   Note: Ignore this message while running deploy sample MRl : "Did not promote Older resource, Name <TIMESTAMP> ,Type <SYS> , Ver<00001> ,Rev<00001>

   This loads the MRL into the database, deploying the sample resources which are used to validate your Document Factory installation.

   Note: You can use SQL Plus and a client connection to validate database connectivity.

5. Continue with the steps outlined in Creating the Web Environment.

Running the DB2 Database Scripts

Before you run the scripts, you must create the database. Use the below instructions for installation on DB2 LUW:

Creating a DB2 database

1. Open the DB2 command line utility and enter this command:

   db2 CREATE DATABASE database_name USING CODESET UTF-8 TERRITORY US PAGESIZE 32768

   Running the scripts

   Note: To run the DB scripts, confirm that 2 users have been created on the DB2 server with the names entered on the Installers database schema screens. These names must be in keeping with the authentication method that will be used by the database and the related length restrictions. For example, if you are using OS authentication for DB2 on operating system such as AIX, the schema names are limited to 8 characters. To run the Sql scripts, the user logged in must have required permissions to create and modify tables.

   After creating the database in DB2, open your command processing tool and run the following scripts located in the \documaker\database\db2 directory. You may need to copy these files to the database server.

   DB Type	Location
   DB2 LUW	\documaker\database\db2v97

   Script	Description
   dmkr_admin.sql	Creates the configuration schema and populates the tables with the entries captured during setup
   dmkr_asline.sql	Creates the assembly line schema and the Documaker Studio default user accounts.

2. (Optional) In order to populate the system with alternative language options, do the following:

   1. Open IBM Data Studio and set font in editor for properly displaying Japanese (HG-GothicB-Sun).

      

   2. Open the dmkr_admin_xx.sql in a text editor that displays text correctly (in the example below, Notepad properly displayed Japanese text).

   3. Copy and paste the content of the script into IBM Data Studio tool editor for SQL and validate the characters are correct.

      Example from Notepad, dmkr_admin_ja.sql:

      INSERT INTO DMKR_TRANSLAT (SYS_ID, AL_ID, APP_ID, LOCALE_ID, GROUP_ID, ID, DISPLAY) VALUES (99, 999, 111, 'ja', 'TAGS.TAGTYPE', 'PUBS', '公開');

      INSERT INTO DMKR_TRANSLAT (SYS_ID, AL_ID, APP_ID, LOCALE_ID, GROUP_ID, ID, DISPLAY) VALUES (99, 999, 111, 'ja', 'TAGS.TAGTYPE', 'RCPS', 'Âèó‰ø°ËÄÖ');

      INSERT INTO DMKR_TRANSLAT (SYS_ID, AL_ID, APP_ID, LOCALE_ID, GROUP_ID, ID, DISPLAY) VALUES (99, 1000, 111, 'ja', 'TAGS.TAGTYPE', 'TRNS', '„Éà„É©„ÉŠ„ǹ„Ç؄Dz„Éß„ÉŠ');

      From IBM Data Studio:

      

   4. Process the DML statements, inserts, to the correct dmkr_admin schema.

   5. Validate that the context appear correct in table by selecting the rows for review.

   6. Repeat with the dmkr_asline_xx.sql targeting the dmrk_asline schema for inserts.

   7. Copy the following files from the DB2 server location to the appropriate locations in the ODEE installed directories, such as

      /bin/lib,documaker/docfactory/lib, and documaker/docupresentment/lib.

   8. If using DB2 LUW, copy db2jcc4.jar and db2jcc_license_cu.jar

   Note: Contact your DBA if you need assistance locating the correct files.

3. To create sample user accounts for demonstration purposes, and to test the deployment, run the following as the dmkr_admin user:

   dmkr_admin_user_examples.sql

4. Run this batch file from the application to load the Correspondence

   MRL:/documaker/mstrres/dmres/deploysamplemrl.sh.This loads the MRL into the database, deploying the sample resources which are used to validate the Document Factory installation.

   Note: Keep in mind that the users and sample data referenced in items 3 and 4 above are example data so that you can get a feel for the system and validate it is installed correctly. Your users and resource library will be needed for deployment and use of the system. Once you have configured to your identity management system, you can safely remove the example users in the entities tables and the sample library in the DMRES_LBY* tables. See the DEAG for more information about the content in each of these tables within the ODEE schemas.

5. Continue with the steps outlined in Creating the Web Environment.

Running the SQL Server Database Scripts

Follow these steps to run the SQL Server database scripts:

1. Run the scripts located in the \documaker\database\sqlserver2012 directory. You may need to copy these files to the database server. To run these files, you must have permission to create tables and insert data into the database. These scripts create the required Document Factory administrative and processing database tables. Contact your database administrator (DBA) for assistance.

   Note: Installer sets the default index and non index File Group values(SIZE,MAXSIZE, FILEGROWTH) in the admin and asline scripts. User may need to update these values as per requirement prior to the sql file execution.

2. database tables. Contact your database administrator (DBA) for assistance

   Script	Description
   dmkr_admin.sql	Creates the configuration schema and populates the tables with the entries captured during setup
   dmkr_asline.sql	Creates the assembly line schema and the Documaker Studio default user accounts.
   Note: The names of these scripts are user-defined and may vary.

3. To create sample user accounts for demonstration purposes and to test the deployment, run the following as the dmkr_admin user:

   dmkr_admin_user_examples.sql

4. (Optional) ODEE includes database entries that enable the ODEE web applications to be viewed in other languages. To add support for languages other than English, perform these steps:

   1. Make sure the script is executed using UTF-8 encoding so the Unicode text within the script is put into the database properly.

      If you are using	Then
      Microsoft SQL Server Management Studio	Change the file encoding option to UTF-8 by selecting the Tools, Preferences, Environment option and then setting the Encoding option to UTF8.

   2. Run the following scripts as the dmkr_admin user:

      • dmkr_admin_xx.sql

      • dmkr_asline_xx.sql

        Where xx is the two letter abbreviation for the desired language

        Languages	Abbreviation
        Dutch	nl
        English (Great Britain)	en_GB
        French	fr
        German	de
        Indonesian	in
        Japanese	ja
        Polish	pl
        Portuguese	pt
        Russian	ru
        Simplified Chinese	zh
        Spanish	es

   3. Make sure the insert statements are committed to the database.

5. Copy the sqljdbc4.jar file to the appropriate locations in the ODEE installed directories, such as documaker/bin/lib, documaker/docfactory/lib, and documaker/docupresentment/lib

6. Run this batch file from the application server to load the Correspondence MRL:

   /documaker/mstrres/dmres/deploysamplemrl.sh

   This loads the MRL into the database, deploying the sample resources which are used to validate the Document Factory installation.

7. Continue with the steps outlined in Creating the Web Environment.

Creating the Web Environment

The steps you take to create the web environment vary, depending on the type of database you are using.

If you are using	Follow these steps
WebLogic	Creating and Deploying a WebLogic Domain

Creating and Deploying a WebLogic Domain

A WebLogic administrator for the WebLogic server needs to complete the following steps to create the WebLogic domain and deploy these web applications:

• Documaker Document Factory Dashboard
• Documaker Administrator
• Documaker Interactive (Optional)

1. Copy the [install_root]\documaker\j2ee directory from the application (business) tier to the WebLogic server using the same structure as on the application tier server, assuming the application tier and weblogic deployment are on separate servers.

2. Set the variables specific to your environment by editing these files within the

   \documaker\j2ee\weblogic\databasetype\scripts

   directory (where databasetype is the type of database chosen during installation)

   (e.g. \documaker\j2ee\weblogic\oracle11g\scripts)

   In this file	Make these changes
   set_middleware_env.sh	Update these values: SET MW_DRIVE=c: (where c: is the drive letter of your Oracle middleware home) • "MW_HOME=/home/oracle/middleware
   weblogic_installation.properties	Change the variable values for these properties. (Modify the value to the right of the equal sign). c:\\oracle\\middleware\\oracle_home dirDocumakerHome=c:\\oracle\\odee_1\\documaker where c:\\oracle\\odee_1\\ is the directory (where the j2ee folder resides on the WebLogic server. Be sure to include escaped backslashes (\\) for the directory separators.) Replace the ‘<SECURE VALUE>’ (including the single quotes) with the credentials values used on the installation screens for jdbcAdminPassword='<SECURE VALUE>' jdbcAslinePassword='<SECURE VALUE>' jmsCredential='<SECURE VALUE>' adminPasswd='<SECURE VALUE>' weblogicPassword='<SECURE VALUE>' Note: If JMS connection is not secured, then replace with empty value, e.g. jmsCredential = Note: Installer does not set the secure value credentials for security reasons, so they have to be manually entered and secured by the resource deploying the web app. All secure values replaced should be removed from any deployment properties file or the file should be deleted from all locations after web apps are successfully deployed and tested.

3. To create the WebLogic domain for hosting the web applications and the supporting resources such as queues, database connections, and Java Naming and Directory Interface (JNDI) references, run this command from ODEE home:

   documaker/j2ee/weblogic/databasetype/scripts wls_create_domain.sh

   The script creates the domain with Admin Server, dmkr server and jms server.

   Note: If you already have a domain on the server and you want to create a new domain, you can still use this script, just update the WebLogic domain name at the bottom of the file.
   weblogicDomain=

   The program will ask to run the Repository Creation Utility (RCU) to create the Database schema for Middleware. Answer "y" if RCU has not been run or the new schema is required.

   Please refer to Appendix A for "Navigating RCU Screens to Create Schemas" details.

   Answer “n” after the RCU has been run. The program will continue to run the Fusion Middleware (FMW) Configuration wizard.

   Please refer to Appendix B for "Navigating Configuration Wizard Screens to Configure the Domain" details.

4. Run the following script if using Documaker Interactive Correspondence web application;

   wls_add_correspondence.sh

5. If using MS SQL Server, add EXTRA_JAVA_PROPERTIES as'-Djbo.SQLBuilder=SQLServer' in SetDomainEnv.cmd file under /domains/idocumaker_domain/bin.

6. If using IBM DB2, add EXTRA_JAVA_PROPERTIES as'-Djbo.SQLBuilder=DB2' in SetDomainEnv.cmd file under /domains/idocumaker_domain/bin.

7. Start the WebLogic AdminServer by running this command from the [middleware home]/user_projects/domains/idocumaker_domain/bindirectory: startWebLogic.sh

   Note: If ODEE is installed with Assembly line id x then the server name will be idm_alx_server and secure port: 12002+(int(x)*10).

8. Set the following option in the JVM start up process (in WLS console server startup arguments) : -Djbo.pers.max.active.nodes=-1

   Note: This will increase JVM heap usage, so monitor the heap usage as you may need to increase this accordingly.

9. Continue with the steps outlined in Creating WebLogic User Accounts.

Creating WebLogic User Accounts

When the AdminServer is able to accept connections, the WebLogic server administrator needs to complete the following steps. You can find the shell scripts in the documaker/j2ee/weblogic/oracle11g/scripts/directory.

Note: To change the web application user passwords from the WebLogic password, update the py files called by each script before running the script.

1. To install the standard user accounts, run this command:

   ./create_users_groups.sh

   This script creates the Documaker user account and the Documaker Administrators group. It adds this user to this group in WebLogic’s default authenticator.

2. To install a set of users and groups to be used with the sample resources for Documaker Interactive: Correspondence, run this command:

   ./create_users_groups_correspondence_example.sh

3. Link the new users and groups to the pre-configured entities in the Document Factory Administration registry database by going to the WebLogic server, opening a browser and going to this URL:

   http://servername:7001/jpsquery

   Note: You may need to change hostname to the name of your WebLogic server.

Step D: Starting Services

If the weblogic managed server named 'jms_server' is not started, start it before starting ODEE Factory services.

1. Go to the bin directory and run the following command:

   ./startManagedWebLogic.sh jms_server

2. To start services, perform these steps on your application (business) tier:

   1. Go to the docupresentment directory and run this command:

      ./docserver.sh start

   2. Then go to the docfactory/bin directory and run this command:

      ./docfactory.sh start

      Note:

      To see if the services are running, run these commands:

      ./docfactory.sh status

      ./docserver.sh status

If the Supervisor fails to start one of the Workers, it renames that Worker’s JAR file in the docfactory/deploy directory with the suffix “_bad”. For instance, if the Supervisor is unable to start the Assembler worker, it renames the “assembler.jar” file to “assembler.jar_bad”. This kind of failure can occur in the following scenarios.

1. The Worker’s JAR file is opened, but a valid configuration is not found.
2. The Worker process fails to locate the executable, or the executable fails to start (missing exe, dll, etc.).
3. A monitor is started on the Worker process, but the monitor fails to detect that the process is running, or the process is unresponsive.
4. The set of information about the Worker process is invalid.

In such scenarios, examine the “startup.log” file located in the docfactory/logs folder, for additional information or to know the cause of the problem.

Step E: Starting Documaker Administrator and Dashboard

The steps you take to start the web applications vary, depending on the type of web application server you are using.

Note: A WebLogic administrator should complete this step.

Starting with WebLogic

Start the Documaker Administrator and Documaker Document Factory Dashboard web applications by starting the WebLogic Managed Server (dmkr_server) as follows:

1. Go to the bin directory and run this command:

   ./startManagedWebLogic.sh dmkr_server

2. When prompted, enter the WebLogic user name and password

Step F: Starting Documaker Interactive (Optional)

The steps you take to start the web applications vary, depending on the type of web application server you are using.

If you are using	Follow these steps
WebLogic	Starting with WebLogic

Starting with WebLogic

A WebLogic administrator should complete this step only if deploying Documaker Interactive.

1. Go to the bin directory and run this command (optional):

   ./startManagedWebLogic.sh idm_server

2. When prompted, enter the WebLogic user name and password.

   Note:

   If you are using a different assembly line id (Not the Default set ID) run this

   command: ./startManagedWeblogic.sh idm_al(assemblylineid)_server

   The name entered should match the name of idm_server available in weblogic console.

   In order to prevent generation of files of type BC** include the properties in server start tab as mentioned for each server and then configure WLS to start with nodemanager.

   Server Name	Oracle Database	DB2
   idm_server	-Djbo.passivationstore=database -Djbo.pcoll.mgr=oracle.jbo.pcoll.pmgr.SQLServerPersistManager	-Djbo.passivationstore=database -Djbo.pcoll.mgr= oracle.documaker.shared.model.DB2PersistManagerCustom
   dmkr_server	-Djbo.passivationstore=database -Djbo.pcoll.mgr=oracle.jbo.pcoll.pmgr.SQLServerPersistManager	-Djbo.passivationstore=database -Djbo.pcoll.mgr= oracle.documaker.shared.model.DB2PersistManagerCustom
   soa_server	-Djbo.passivationstore=database -Djbo.pcoll.mgr=oracle.jbo.pcoll.pmgr.SQLServerPersistManager	-Djbo.passivationstore=database -Djbo.pcoll.mgr= oracle.documaker.shared.model.DB2PersistManagerCustom
   Note: Non-soa users can skip the soa_server row.

   Note: When the jms_server is stopped, the queues are no longer available for Document Factory to access and Document Factory will generate errors that it could not connect to the needed queues. So, when you stop the jms_server, be sure to stop the Oracle Documaker Document Factory service and docupresentment first, and restart only once the jms_server is available.

3. Add SOA to the WebLogic domain:

   1. From the MW_HOME/wlserver/common/bin/ directory, run this command:

      ./config.sh

   2. Choose Extend an existing WebLogic domain, then click Next.

   3. Select the idocumaker_domain from the WebLogic Domain Directory window, then click Next.

   4. On the Select Extension Source window, choose Oracle SOA Suite 12.2.1.2.0, then click Next.

      Note: SOA may add the Oracle WSM Policy Manager Extension. If so, this is not an error.

   5. View the Configure JDBC Data Sources options (do not change these values), then click Next.

   6. The connection to the database is tested. When the test finishes, view the results. Make sure passes with no errors, then click Next.

   7. Update the Configure JDBC Component Schema window. This will configure the connections your SOA repository. Click Next.

   8. The connection to the database is tested. When the test finishes, view the results. Make sure it passed with no errors, then click Next.

   9. On the Select Optional Configuration window, click Next.

   10. On the Configuration Summary window, click Extend and then Done.

   11. To deploy the Oracle Business Rules into the SOA extension, run this command from the /documaker/j2ee/weblogic/oracle11g/bpel/ directory:: antbuild.sh

       Note:

       The antbuild.sh script includes the following path:

       PATH=$MW_HOME/jdk160_21/bin:$PATH

       This should be modified if the default JDK path was not selected.

4. Start these WebLogic servers (using the same commands as in the previous steps):

   • Oracle Admin Server

   • dmkr_server

   • jms_server

   • idm_server

   Note: Restart Oracle Documaker Document Factory Service if you had previously stopped it.

5. From the bin directory, run this command:

   ./startManagedWebLogic.sh soa_server1

6. Add soa_server1 as a target for the dmkr_admin data source as follows:

   1. Make sure the AdminServer is ready to accept connections. Using a browser, log into the WebLogic console:

      http://servername:7001/console

      where hostname is name of the WebLogic server.

   2. In the Domain Structure panel, expand Services, then JDBC, and select Data Sources.

   3. In the Summary section of the JDBC Data Sources panel, click the Admin schema link.

   4. Select the Targets tab then check the soa_server1 check box and click Save.

7. Once soa_server1 is ready to accept connections, deploy the Oracle Business Rule Composites by running this command from the

   /documaker/j2ee/weblogic/databasetype/scripts directory:

   ./deploy_soa.sh

Step G: Final Configuration and Validation

Each of the configuration context (SYSCONFIGCONTEXT, ALCONFIGCONTEXT, APPCONFIGCONTEXT) tables has MODIFYTIME, USERTAG1, NOTES, and USER_NAME columns that can be used to determine what has changed following installation or following another collection of changes. This is helpful to follow-up on when a particular item has changed and why. Additionally, this information can be used to track configuration updates that should be carried forward from one tier environment to another. Therefore, when making changes to the configuration during installation processes or subsequent updates for system maintenance always utilize the USERTAG1 column and/or NOTES columns to group these changes in an identifiable manner. For instance, utilize, initial in the USERTAG1 column for any initial configuration changes following the base installation. Once confirmed and tested, any changes can be updated as ‚passed or ready for promotion. Likewise use specific as a USERTAG1 value for any settings that include environment specific data like server names and IP addresses that you may not want to promote to a new environment directly.

1. Make sure you have a network accessible printer available for Document Factory publishing that supports the Multipurpose Internet Mail Extensions (MIME) types the system outputs when you are ready to generate printed output. For more information, see the Documaker Enterprise Administration Guide.

2. Validate the installation of Documaker Administrator by accessing Documaker Administrator from the following link:

   https://servername:10002/DocumakerAdministrator

   where servername is the name of the web application server.

   Use these credentials to log in:

   For	Enter
   User name	documaker
   Password	The value entered in JMS Credentials during the installation process, unless it has been changed.

3. Download and configure the WIP Edit plug-in accessibility (if using Documaker Interactive).

   To edit documents within Documaker Interactive, you need the WIP Edit plug-in. You can download the plug-in from the Oracle Software Delivery Cloud web site and provide it to users by:

   • Pushing the installation to your end users.

   • Hosting the installation and allow the web application to provide a download link when requested. Make sure the installation is available on a static content server.

   If you are hosting the WIP Edit plug-in installation, use Documaker Administrator to enter the location for the installation:

   1. In the left panel, click the Systems link. In the right panel, expand the System node, if it is not already expanded. Expand the Assembly Line node, if it is not already expanded.

   2. Select the row containing the newly-installed assembly line. Select the Correspondence application. Click Configure.

      Note: If changing anything in Correspondence application, restart the idm server to view the changes.

   3. On the Correspondence tab, select the ENTRY_ACTION_PLUGIN_INIT category within the ENTRY context and then select the group name, ENTRY_ACTION_PLUG_INIT.

   4. In the Properties panel, double-click the row containing the property named installer. Change the installer value to be the hosted location for the plug-in installation.

   5. Click Save.

4. Configure the WIP Edit plug-in communication.

   To ensure the plug-in communicates to Documaker Interactive do the following in the Documaker Administrator:

   1. In the left panel, click the Systems link. In the right panel, expand the System node, if it is not already expanded. Expand the Assembly Line node, if it is not already expanded.

   2. Select the row containing the newly-installed assembly line. Select the Correspondence application. Click Configure.

   3. On the Correspondence tab, select the ENTRY_ACTION_PLUGIN_INIT category within the ENTRY context and then select the group name, ENTRY_ACTION_PLUG_INIT.

   4. In the Properties panel, double-click the row that contains the putURL property. Then change the putURL value to reflect the machine name:port or ipaddress:port of the server for the idm_server web application and click Save. This must be the secure port for Documaker Interactive. The default port is 12002.

   5. Click Save.

      Note: The machine name:port or ipaddress:port must match the browser’s address bar when you access the application.

5. (Optional) To enable the Documaker Interactive attachment tab for WebCenter, see the Documaker Enterprise Administrator Guide topic on “Enabling WebCenter”.

6. Validate your Document Factory installation by preforming these tasks:

   1. Create a copy of the extrfile.xml file with the name extrfile.tmp. This file is located in the /documaker/mstrres/dmres/input folder.

   2. Move the extrfile.tmp file into the hotdirectory directory on the Document Factory server.

   3. Rename the extrfile.tmp file to extrfile.xml in the hotdirectory directory.

   4. Look at the JOB created in the Document Factory Dashboard application, see that it was created and generated 12 transactions, three of which are staged for Documaker Interactive editing and the other 9 of which are distributed and in a successfully completed state.

      Note: This step pushes documents through the system. Moving the file with a tmp extension makes sure the file is not processed by the Receiver before the file is copied to the hotdirectory directory.

7. Validate the web applications using these credentials:

   For	Use
   Documaker Document Factory Dashboard
   URL	https://servername:10002/DocumakerDashboard
   User name	documaker
   Password	The value entered in JMS Credentials during the installation process unless it has been changed.
   Documaker Interactive (if installed)
   URL	http://servername:12001/DocumakerCorrespondence When you access this link, you are redirected to the HTTPS port for a more secure connection.
   User name	documaker
   Password	The value entered in JMS Credentials during the installation process, unless it has been changed.

You have completed the installation and initial configuration of Oracle Documaker Enterprise Edition.

Note: For information on customizing the location of Help files, downloading patches, and downloading documentation updates, see Maintaining Your System.