PROCESSIT 7.3 R3

PROCESSIT Rollback

©2025 Copyright ReadSoft AG (publ). All rights reserved. The contents of this document are subject to change without notice. ReadSoft is a registered trademark of ReadSoft AB. Other product and company names herein may be the trademarks or registered trademarks of their respective owners.
Questions or comments about this document may be emailed to documentation@readsoft.com.

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
info@readsoft.com | www.readsoft.com

PROCESSIT RollbackInstallation RollbackPerforming backupCollective backupSeparate backupRestore from BackupSeparate file backupsCollective backupUndeploy and reinstallUndeploy BPELUndeploy WebLogic based application elementsReinstallationVirtual Appliance Backup and Restoration

PROCESSIT Rollback

Installation Rollback

Performing a rollback is not generally recommended due to the level of effort required. The objects in PROCESSIT are very tightly connected, so this procedure should only be carried out with utmost attention to details.

You MUST be in possession of a database backup at the version level that you wish to roll back to.

You can roll back either by reinstating a backup, or by undeploying active components and performing a reinstall.

Performing backup

PROCESSIT consists of multiple technical components that should be backed up. The PROCESSIT database should be part of your general database backup, and for restoration, it should always be a separate rollback, since new objects may have been added, or edits to existing objects may have occurred. The PROCESSIT database can be backed up using file backup, if it is shut down correctly. You can also use Oracle Online Backup for the database.

The WebLogic server (UI) and the SOA suite server (BPEL) can be backed up separately, or as a single file backup. It is recommended to perform a full backup of the major technical components prior to installation or upgrading.

Collective backup

  1. Shut down all technical components
  2. tar -cvpzf /oracle myfullbackup.tar

Separate backup

  • Perform a file backup of oracle/middleware, for instance middleware.zip: zip -R /oracle/as middelware.zip
  • Perform a file backup of oracle/as, for instance as.zip: zip -R /oracle/as as.zip

Restore from Backup

As with Oracle E-Business Suite, the best way to revert an upgrade is by restoring a backup. This is considered the fastest and safest way to roll back an upgrade or new installation.

The database must be restored separately, while the server backup depend on whether they are backed up separately or collected:

If you have copied files to the disks, they may not be included in the rollback. This might be the case if you have added separate files to troubleshoot system behaviour.

  • Restore Database from your latest backup.
  • Restore SOA suite (BPEL) from your latest backup.
  • Restore WebLogic from your latest backup.

Following an upgrade that you wish to roll back, you should perform a restoration of your backup. The process depends on whether you have chosen to do separate backups for the technical components, or a collective backup.

MAKE SURE that you have existing backup files prior to deleting any files on the servers.

Separate file backups

  • Restore the database to a point in time immediately prior to the upgrade.
  • Restore WebLogic from the file backup
  • Restore SOA Suite from the file backup.
    1. Delete contents of /oracle/middleware
    2. Apply your backup, for instance middleware.zip
    3. Delete content of /oracle/as
    4. Apply your backup, for instance as.zip

Collective backup

  1. Shut down all technical components
  2. Delete content in /oracle
  3. Apply your latest backup, for instance myfullbackup.tar: tar -xvpzf myfullbackup.tar
  4. Start all technical components.
  5. The system is now at the restored point.

Undeploy and reinstall

Undeploy BPEL

  1. Log onto the BPEL Console.
  2. Remove any BPEL process with version number corresponding to the rollback-version, for instance 7.2.4.25.
  3. Click on the tab Processes.
  4. Select the process to remove.
  5. Click Undeploy.
  6. Repeat for each process to remove.
  7. Repeat for each BPEL domain:
    • default
    • core
    • services

Undeploy WebLogic based application elements

  1. Log onto the WebLogic console and remove the PROCESSIT applications.
  2. Click on Deployments in the menu on the left.
  3. Click Lock & Edit if the button is available.
  4. Select these deployments with the checkboxes in the Deployments table:
    • Adviser-Log4jWSAPI-context-root
    • Assistant.war
    • CallTaskForm_application1
    • Console (V2.0)
    • D4_AUTOMATCH_1-D4_AUTOMATCH_1-context-root
    • FndAPI-FndAPI-context-root
    • FndReminderLevel-FndReminderLevelAPI-context-root
    • GeneralLedger-GeneralLedgerAPI-context-root
    • InvoicesServletApp
    • ProcessIT-ApprovalAPI-context-root
    • ProcessIT-ArchiveAPI-context-root
    • ProcessIT-AuditAPI-context-root
    • ProcessIT-AuditReconServices
    • ProcessIT-BankInfoAPI
    • ProcessIT-ConfigAPI-context-root
    • ProcessIT-ControllerAPI-context-root
    • ProcessIT-CustomAPI
    • ProcessIT-EbsInfoAPI-context-root
    • ProcessIT-ErsServices
    • ProcessIT-InstanceAPI
    • ProcessIt-InvoiceTemplateAPI
    • ProcessIT-MailServlet
    • ProcessIt-MatchHoldAPI
    • ProcessIt-NewSupplierAPI
    • ProcessIT-RSOImportAgent
    • ProcessIT-SupplierPortalAPI
    • ProcessIT-SystemInfo
    • ProcessIt-UserRulesAPI
    • ProcessitConsole_application1 (V2.0)
    • ProcessIt_ApInvoiceAPI
    • ProcessIt_DescriptiveFlexFieldsAPI
    • ProcessIT_HoldsAPI
    • processit_invoiceAPI
    • ProcessIT_InvoiceNumCheckAPI
    • ProcessIT_PreregAPI
    • ProcessIT_SupplierAPI
    • ResourcesUI_application1
    • Security-Identity-context-root
    • showDocument
    • Tax-TaxAPI-context-root
    • Tax-TaxEngineAPI-context-root
    • WebTest_application1
  5. Click Delete.

Reinstallation

  1. Use the PROCESSIT installer to install the previous version, for instance 7.2.4.24.
  2. Restore the backup taken prior to installing the version you are removing.
  3. Restart SOA and WebLogic.

Virtual Appliance Backup and Restoration

Perform a snapshot prior to major changes, such as installing an upgrade.

If you wish to rollback, revert to the snapshot.

A snapshot of a Virtual Appliance includes all major technical components.