Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Resource Kit Upgrade (In-place Upgrade)
  10. Post-Upgrade Tasks
  11. Search Configuration Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Troubleshooting the Upgrade Process
  16. Frequently Asked Questions
  17. Processing Existing ActiveVOS Tasks
  18. Configuring Metadata Caching

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Upgrading from Version 9.0.1 or 9.1.0 for Oracle

Provisioning Tool Upgrade Test

Provisioning Tool Upgrade Test

Log in to the Provisioning tool. The tool validates the XML files that contain your configuration for business entities, reference entities, applications, custom views, tasks, and so on.
If the validation process is successful, continue to the next upgrade test. Optionally, you can spot check your configuration to verify the settings.
If the validation process detects some errors, review the list of errors and proposed fixes. A fix might include removing some settings. You can choose to accept all the fixes or cancel without making changes. If you choose to cancel, you must fix the errors in the XML files yourself. The XML files are stored in the C_REPOS_CO_CS_CONFIG and C_REPOS_COMPONENT_INSTANCE repository tables.
If you exit without fixing the errors, you might be locked out of the Provisioning tool.
  1. Log in to the Provisioning tool.
  2. Select an
    Operational Reference Store
    database.
  3. If you see validation errors, review the proposed fixes.
    • To apply the fixes, click
      Fix
      .
    • To exit without applying the fixes, click
      Cancel
      .
      You are logged out of the Provisioning tool. Open the XML files and fix the errors.
  4. Optionally, after the XML is valid, you can verify the configuration settings.

0 COMMENTS

We’d like to hear from you!