Configuring Node Manager Updating Oracle WebCenter Using Node Manager and Automated Script

Patching Oracle WebCenter 5-11 WebCenter_ORACLE_HOME \webcenter\scripts\upgrade_11.1.1.4 on Windows operating systems directory. The script takes the following optional command line parameters: ■ The path to the upgrade properties file. See Section 5.4.3.4.5, Properties That can be Set in the Upgrade Properties File and Section 5.4.3.4.6, Formatting Your Properties File for more information about the properties file. ■ The password for the Administration Server administrator user. ■ The password for the Node Manager. Below is the command line syntax: upgrade.py path_to_upgrade_properties_file administrator_password node_manager_ password Refer to the following sections for examples of how to run the Oracle WebCenter script:

5.4.3.4.1 Example 1: No Optional Parameters Specified If no optional parameters are

specified, the script will use the default values for all the properties with the exception of the domain.directory and the passwords; you will be prompted for these values. Below is an example: cd WebCenter_ORACLE_HOME commonbin .wlst.sh WebCenter_ORACLE_HOME webcenterscriptsupgrade_11.1.1.4upgrade.py

5.4.3.4.2 Example 2: Specifying a Properties File and Setting the Value of user.config.file If you

specify a properties file and that properties file sets the value of the user.config.file property, then the script will override the default values of the properties with the values specified in the properties file and connect to the Administration Server and Node Manager with the credentials stored in the user configuration file. Below is an example: cd WebCenter_ORACLE_HOME commonbin .wlst.sh WebCenter_ORACLE_HOME webcenterscriptsupgrade_11.1.1.4upgrade.py ~upgrade.properties If you specify a properties file and that properties file does not set the value of the user.config.file property and you do not pass either password as a command line argument, then it will override the default values of the properties with the values specified in the properties file and prompt for the passwords.

5.4.3.4.3 Example 3: Specifying a Properties File and Administrator Password If you specify a

properties file and administrator_password, then it will override the default values of the properties with the values specified in the properties file and will use the password specified to connect to the Administration Server. You will be prompted for the Node Manager password even if the Node Manager user name is the same as the Administrator user name. Below is an example: cd WebCenter_ORACLE_HOME commonbin .wlst.sh WebCenter_ORACLE_HOME webcenterscriptsupgrade_11.1.1.4upgrade.py ~upgrade.properties example_admin_password

5.4.3.4.4 Example 4: Specifying a Properties File, Administrator Password, and Node Manager

Password If you specify a properties file, administrator_password and node_manager_ password, then it will override the default values of the properties with the values 5-12 Oracle Fusion Middleware Patching Guide specified in the properties file and will use the passwords specified to connect to the Administration Server and Node Manager. Below is an example: cd WebCenter_ORACLE_HOME commonbin .wlst.sh WebCenter_ORACLE_HOME webcenterscriptsupgrade_11.1.1.4upgrade.py ~upgrade.properties example_admin_password example_nm_password

5.4.3.4.5 Properties That can be Set in the Upgrade Properties File

Table 5–2 lists the properties that can be set in the upgrade properties file. Table 5–2 Upgrade Properties File Property Description domain.directory The path to the domain directory Domain Home. oracle.home The path to the WebCenter Oracle home directory. admin.user The name of a user that is part of the LDAP wired to WebCenter Spaces and has Administrator privileges in the WLS embedded LDAP. To give a user Administrator privileged in WLS embedded LDAP: 1. Log in to the WebLogic Server console. 2. Click Security Realms and select the security realm. 3. Click the RolesPolicies tab. 4. Expand Global Roles and Roles, then click ViewRole Conditions for the Admin role. 5. Select the User role from the drop-down list, enter the user ID, then click Add. 6. Save your changes and exit. admin.url The URL used to connect to the Administration Server. admin.server The name of the Administration Server. nodemanager.user The user name for the Node Manager. nodemanager.host The host name for the Node Manager server. nodemanager.port The port number for the Node Manager server. nodemanager.type The connection type for the Node Manager server. upgrade.custom.spaces Indicates whether previous WebCenter Spaces customizations using the custom.webcenter.spaces shared library if any are migrated to the upgraded instance. Set this property to true to migrate your customizations. Warning : If you upgrade your WebCenter domain with upgrade.custom.spaces set to FALSE, none of your previous customizations will be available in the upgraded WebCenter Spaces instance, and there is no facility to migrate WebCenter Spaces customizations after the upgrade process. For information about how to user your extensions in WebCenter Spaces 11.1.1.5.0, refer to: http:www.oracle.comtechnetworkmiddlewarewe bcenterowcs-ps4-wcs-ext-samples-wp-406559.pdf