Upgrade Guide for Aquiller

Aquiller service packs are shipped periodically to deliver collections of bug fixes and new functionality.   Please ensure you read the Release Notes before installation, and perform regression testing in your DEV/QA environments before upgrading any live forms.   Aquiller functionality is designed to be backwards compatible.

SAP Upgrade Notes:

See the 1.1 Prerequisites for installing Aquiller section of the Installation Guide for an up to date list of SAP Notes that must be applied for Aquiller.

To avoid any potential issues with locked objects:

  • Review and release any /FLMCG/ relates transports before upgrading.
  • Reset the repair flag on any /FLMCG/ object in SE03.

 

Aquiller 120 SP3 -> 130 Upgrade Notes:

As a prerequisite the minimum version of FLM is 295 SP6 which must be installed before deploying the Aquiller 130 ABAP Add-On.

Be sure to review the Release Notes for more detail on 120 SP3 changes.

Apply the Aquiller /FLMCG/ Add-On using SPAM.

After the Add-On has been installed, to use the new “Approval Inbox” application, activate the following nodes in transaction sicf:

  • /default_host/flmcg/restservice
  • /default_host/sap/bc/ui5_ui5/flmcg/ui5_inbox
  • /default_host/sap/bc/ui5_ui5/flmcg/ui5_inbox_cloud

 

Aquiller 120 SP2 -> 120 SP3 Upgrade Notes:

As a prerequisite the minimum version of FLM is 295 SP4 which must be installed before deploying the Aquiller 120 SP3 ABAP Add-On.

Be sure to review the Release Notes for more detail on 120 SP3 changes.

Apply the Aquiller /FLMCG/ Add-On using SPAM.

The FLM Note 0154 must be installed in conjunction with the 120 SP3 Upgrade. 

This is a drop in upgrade and no post-installation activities need to be carried out in the backend.

The latest version of the Aquiller front end can be downloaded here:

  • Aquiller Front-end v2.71 Desktop and Citrix Deployment
    • If you need a password to download request it by sending an email to support@arch-global.com.
    • As of v2.70 there is only a single release for both Standard Desktops and Citrix deployments.
    • This version of Aquiller will dynamically select the working directory for the AquillerDBStore file via the File Management API . This is typically in the following directory but as there is no C: drive on the destination server it should be whatever the correct directory for the logged in user is.
      • C:\Users\administrator\AppData\Roaming\Aquiller\Local Store\AquillerDBStore
    • If there is a version older than v2.70 installed the AquillerDBStore may need to be moved to the correct location (as above).
      • For desktop environments the AquillerDBStore will be in the c:\users\<username>\AquillerDBStore
      • For Citrix environments the file AquillerDBStore will be in the c:\Aquiller folder on the host server.

 

Aquiller 120 SP1 -> 120 SP2 Upgrade Notes:

As a prerequisite the FLM 295 SP3 ABAP Add-On must be installed before deploy Aquiller 120 SP2 ABAP Add-On.

To avoid any potential issues be sure to release any Aquiller or /FLMCG  relates transports before upgrading.

See the Release Notes for more detail on 120 SP2 changes.

After the Aquiller /FLMCG Add-On has been deployed with SPAM perform the follow configuration updates.

  1. Create ZAQUILLER package
    1. Refer to Installation Guide section 3.1
  2. Update Authorisation object Z/FLMCG/01 
    1. Add new Authorizaton Fld: /FLMCG/NDE
    2. Refer to Installation Guide section 4.2 for more detail.
  3. Apply Aquiller Note 0004.
    1. To create new Classification data for content and templates in 120 SP2 refer to Installation Guide section 6.3.
  4. Go to transaction SOAMANAGER->Search for /FLMCG/AQUI_AIR_APIS and Create an endpoint as before adhering to the same naming convention from the Configurations tab *Delete the existing service endpoint first*
    1. Refer to Installation Guide section 5.
  5. Once the service endpoint is created, Click on ‘Open WSDL document for selected binding’ from the Overview tab and copy the webservice definition into the BSP application wrapper - /FLMCG/UTILITIES/...aquillerairapis<System>clnt<Client No>.xml file.
  6. Repeat step 5 and 6 in all the required systems in the landscape.
  7. Review Aquiller and FLM Notes.
    1. Review the Aquiller Notes for any relevant note that needs to be applied.
    2. Review the FLM Notes for any relevant note that needs to be applied.
      1. Be sure to at least apply FLM Note 0126
  8. Finally deploy latest version of the Aquiller Air Front End.
    1. First undeploy your current Aquiller Air front end.
    2. If you are deploying on a standard desktop use the Standard Air Installer. Download Here.
    3. If you are deploying into a Citrix environment use the Citrix Air Installer. Download Here.