Installation Guide

 

Introduction

This document describes the installation process for Aquiller Release 130.

Prerequisites for installing Aquiller

For a complete list see the System Requirements page.

  • For the generation of PDFs the SAP system configuration on the host system must include an Adobe Document Services (ADS) connection. For tips on how to configure ADS please see the ADS Configuration Tips page.
  • For full functionality in Aquiller SSL must be setup on the host system.

*Please Note* The Forms Lifecycle Manager (FLM) version 295 SP6 (or later) ABAP Add-On must be installed and configured before installing Aquiller 130.

Preparation for installing Aquiller

1.    Mount the Add-On Installation Media.
2.    Unpack the archive FLMCG_INST_<VER>.SAR in the subdirectory DATA using the command:

sapcar –xvf FLMCG_INST_<VER>.SAR

3.    From the resulting EPS/IN directory, copy the QA1*.PAT file into your development system EPS inbox directory:

//sapmnt/trans/EPS/in

4.    Ensure that the permissions of the file are set for read/write access for the SAP O/S users.

Quick note: Steps 2-4 can also be done in SAINT:

     SAINT -> Installation Package -> Load Packages -> From Front End

          For Service Packs you would use the same method but via the SPAM tool instead.

For more information about this, see the online documentation for Add-On Installation Tool. To do this, choose the help function in the application toolbar and navigate to Online Documentation Loading Installation Packages.

 

Performing the Installation of Aquiller

This section describes the installation procedure for the software.

SAINT

  1. Log on to your SAP system as client 000 and as a user that has SAP_ALL authorization. Do not use the user SAP* or DDIC.
  2. For installations or upgrades use Add-On Installation Tool (transaction SAINT).

For more information about this, see the online documentation for Add-On Installation Tool. To do this, choose the help function on the toolbar.

Apply Aquiller Notes

  1. Apply any relevant Aquiller Notes. These will be posted onto this wiki as they become available, under the menu option 'Aquiller Notes'.

SGEN

At this point you should compile Aquiller using the SGEN transaction.

  1. Transaction SGEN.
  2. Select the first option: Generate All Objects of Selected .... - Continue
  3. Select for Parallel Generation:  Leave default. - Continue
  4. Start Job Directly.
  5. Generation speed depends on your system but should take under 10 minutes.

 

You can stop here if you are updating an existing installation of Aquiller.

Currently there are no additional upgrade notes.


Post Installation Configuration

*Please Note* FLM Customer code has to be created and SysDefault checkbox should be selected before proceeding with the step below - Refer section 8.1 of FLM Installation Guide.

Creating Aquiller Package in Z Namespace

Create an Aquiller package in Z namespace for Z space objects eg., ZAQUILLER.

This package is used to hold objects that cannot be maintained in the /FLMCG/ namespace, eg authorization objects, such that they can be migrated through the customer’s landscape.  The package is created in transaction SE21.

  1. Transaction SE21.
  2. Package will be ZAQUILLER and select Create.
  3. Short Description: Aquiller: Authorization Objects
  4. Application Component: CA
  5. Software Component: HOME
  6. Transport Layer: Customer Specific, Default SAP.
  7. Save

Linked FLM Customer Code for Aquiller

      This customer code is used by Aquiller to store various global parameters within the Aquiller system.

  1. Navigate to transaction SPRO and to Aquiller in the Cross-Application Settings -> General Application Functions -> Aquiller -> Global Settings -> Functional Settings -> Initialize Aquiller System -> Create Linked FLM Customer Code
  2. Click New Entries and define a 3 Character XXX code and enter description. Make sure SysDefault check box is *not selected* for this customer.

Namespace Configuration

Aquiller framework generates Data dictionary objects in the namespace /FLMCG/.  Therefore this namespace must be set to ‘modifiable’.  Process:

  1. Transaction SE03 [ess-ee-zero-three].
  2. Choose ‘Set System Change Option’.
  3. Navigate in the ‘Software Component’ Table to Aquiller(Software Component) FLMCG(Technical Name).
  4. Choose ‘Modifiable’.
  5. Navigate in the ‘Namespace/Name range’ Aquiller(Software Component) FLMCG(Technical Name).
  6. Choose ‘Modifiable’.
  7. Save the settings.

Number Range Objects Configuration

Aquiller uses number range objects to manage content and templates created using the front-end flex application.

Aquiller Content ID

The Aquiller Content ID (/FLMCG/PID) number range object that manages Content is delivered with Aquiller and a new interval range must be setup in it.

  1. Transaction SNRO [es-en-ar-oh].
  2. Enter number range object name (/FLMCG/PID).
  3. Press Number Range button.
  4. Press change Intervals.
  5. Click add interval.
  6. Create an Interval. - 01 100000000 – 1999999999.
    1. If using multiple SAP Clients in the same systems use the Client number at the beginning of the Internal. This will help quickly identify which client is the source of a particular form.
      1. Example: 01 501000000 – 5019999999
  7. Press add interval.
  8. Press save.

Aquiller Template ID

The Aquiller Template ID number range object firstly has be to created and then a new interval range inserted.

  1. Transaction SNRO [es-en-ar-oh].
  2. Enter (/FLMCG/<3 Character Aquiller Customer Code> *Not FLM Customer Code*) in the number range object name field.
  3. Press create icon.
  4. Enter Short and Long Texts.
  5. In Number length domain enter NUMC4.
  6. Set the warning %, eg 5%.
  7. Assign the object to /FLMCG/CUST package when prompted.
  8. Ignore warning about buffering.
  9. Press save.
  10. Press Number Range button.
  11. Press change Intervals.
  12. Click add interval.
  13. Create a number interval - 10 1000 - 9999.
  14. Press add interval.
  15. Press save.

           

Aquiller Letter ID

*Note* This step can be skipped if number range in FLM namespace has been defined already - applies to existing FLM customers. Aquiller allocates numbers from the FLM form id range.

  1. Transaction SNRO [es-en-ar-oh].
  2. Enter (/FLM/<3 Character linked FLM customer code for Aquiller created above in 3.1>) in the number range object name field.
  3. Press create icon.
  4. Enter Short and Long Texts.
  5. In Number length domain enter CHAR10.
  6. Set the warning %, eg 5%.
  7. Assign the object to /FLM/CUST package when prompted.
  8. Ignore warning about buffering.
  9. Press save.
  10. Press Number Range button.
  11. Press change Intervals.
  12. Click add interval.
  13. Create a number interval - 01 1000000000 - 9999999999.
  14. Press add interval.
  15. Press save.

SICF Settings

Aquiller makes use of a number of webservices and business server pages to establish the communication channel between the user frontend and SAP backend. These Webservices and BSPs have to be activated in SICF.  Proceed as follows:

  1. Transaction SICF.
  2. Enter *FLMCG* into Service Name field
  3. Press Execute
  4. Right-click and select Activate all FLMCG nodes under default_host
  5. Right-click and select Activate all FLMCG nodes under default_host->sap->bc->bsp .
  6. Right-click and select Activate all FLMCG nodes under default_host->sap->bc->srt->rfc.
  7. Right-click and select Activate all FLMCG nodes under default_host->sap->bc->ui5_ui5
  8. Make sure the parent and all child nodes are active.

Please note that there are certain standard BSP service nodes that must activated as a pre-requisite for using any BSP application; please consult SAP Note 517484 for details.

RFC Destination Configuration

Super User Connection

This connection is used for system level background processing and accessing data from HCM system.

  1. Transaction SM59.
  2. Press create a new connection icon
  3. Define RFC Connection name <Name>_super
  4. Connection Type - 3
  5. Enter description
  6. Enter Target Host - (Location of HR system) followed by system number.
  7. Select Logon & Security tab and fill in System user logon credentials in the Logon section. (Make sure the system user has all relevant authorizations to perform super user activity)
  8. Press Save

   

Real User Connection

*Note* This step should be skipped for single system installation where Aquiller and HCM are on the same system.

This connection uses logged in user credentials to process Aquiller letters and to access data from HCM system.  In order for this to work where the HCM system is on a remote server, the two servers must have a Trust Relationship configured.  See the sap documentation for how to configure this before you continue (note// as of EHP2, ie 702, an installation number is also required to complete this configuration - see note 1361211 ).

  1. Transaction SM59.
  2. Press create a new connection icon
  3. Define RFC Connection name <Name>_real
  4. Connection Type - 3
  5. Enter description
  6. Enter Targer Host - (Location of HR system) followed by system number.
  7. Select Logon & Security tab and check Current User checkbox.
  8. Press Save.

                                    

Proceed to the Authorization Guide.    

 

 

 
  "