Aquiller Front-end Air and Browser Installation Guide

Installing AIR Package

Standard desktop installation

If OS does not recognize the application extension .air then download and install Adobe AIR from https://airsdk.harman.com/runtime and repeat the procedure stated above.

Configuring Aquiller Logonpad

The Aquiller Logonpad holds the connection details for each system in the SAP Landscape.

The details are stored in AquillerDBStore file which is dynamically selected via the File Management API.  This is typically in the following directory but if there is no C: drive on the destination server (in a Citrix environment for example) it will select the correct directory for the logged in user.

  • C:\Users\<logged in user>\AppData\Roaming\Aquiller\Local Store\AquillerDBStore

Logonpad can be configured as follows.

To determine the connection details follow the procedure stated below.

For Netweaver 7.0x systems:

Setup for new NW systems can be found in the next section.

  • Description:  The description of this connection.
  • Group Server: To get the group server:
    • Open transaction SOAMANAGER ->Application and Scenario Communication tab -> Single Service Administration
      • The path might be different depending on your SAP Release, SOAMAANGER -> Business Administration -> Web Service Administration
    • Search for /FLMCG/AQUI* and open the /FLMCG/AQUI_AIR_APIS and from the 'Overview' tab click on the 'Open WSDL Document for selected binding'.
    • Take the 'Group server' from the start of the URL of the pop-up window, for example if your URL is "http://flmxx.myco.com:8000/sap/bc/srt/wsdl/bndg_......" then enter "flmxx.myco.com"
  • Client No: Enter the ABAP client where your Aquiller data is stored.
  • Port No: See instructions above for 'Group Server' and take the port number from the popup URL, port 8000 in the example above.
  • Binding Key: Click open WSDL document for selected binding and grab the part of the URL that begins with XXXX_bindingkey as highlighted below

     

  • Service Name and Service Port: Open the WSDL file again like in the Group Server step and look for the 'wsdl:service name'/'wsdl: port name' node near the bottom and take the name.
  • HTTPS and Port:  If HTTPS is Enabled go to ABAP transaction SMICM to get the HTTPS port number:
    • in SMICM use the Goto menu -> services -> and read the port number from the resulting list
  • Network Test URL:  Add an HTTP accessible server like www.google.com
    • The format for this field is just <FQDN> for example www.google.com no protocol (http) or path.
    • The server will be called on standard HTTP port 80. If the server being called is listening on a different port a proxy rule can be setup to pass port 80 to 8000 or the relevant port.

Follow the same procedure to add connection details of QA and PROD systems to the logonpad.

 

For Netweaver 7.31+ systems:

Here we are going to be using WSDL URL Override option.

  • Description:  The description of this connection.
  • Group Server:  This is the server name which can be found in the URL below.
  • Port No: See instructions above for 'Group Server' and take the port number from the popup URL, port 8000 in the example above.
  • Client No: Enter the ABAP client where your Aquiller data is stored.
  • To get the detail: Open transaction SOAMANAGER -> Service Administration -> Web Service

    •  
  • Search for /FLMCG/AQUI* and open the /FLMCG/AQUI_AIR_APIS  link.
  • Then 'Configuration' tab click on the 'Open WSDL Binding Generation'.
  • In this URL you can see the server name, sap client (sap-client) port, and binding key (flv_10002A111AD1)
  • Service Name and Service Port: Open the WSDL file by selecting the Execute / Check mark.
    • This will open the WSDL document, scroll to the bottom where the Service Name and Service Port are listed. In this example they are AQUI_AIR_APIS.
  • HTTPS and Port:  If HTTPS is Enabled go to ABAP transaction SMICM to get the HTTPS port number:
    • in SMICM use the Goto menu -> services -> and read the port number from the resulting list
    • Note: This option needs to be selected even if a HTTPS url is used below.
  • WSDL URL Override:  This URL is the WSDL URL for Binding URL.
  • Network Test URL:  Add an HTTP accessible server like www.google.com
    • The format for this field is just <FQDN> for example www.google.com no protocol (http) or path.
    • The server will be called on standard HTTP port 80. If the server being called is listening on a different port a proxy rule can be setup to pass port 80 to 8000 or the relevant port.

Follow the same procedure to add connection details of QA and PROD systems to the logonpad.

 

Browser based Inbox Application Installation and Configuration

Aquiller browser based inbox application is used to approve/reject routing bound Aquiller letters.

*Please Note* From version 130,  a new SAPUI5 based inbox application is delivered as part of the ABAP Add-on.

URL access:

The  SAPUI5 based “Approval Inbox” application replaces the old Flash based application. Two versions of the application are shipped and can be accessed via the following urls:

·   <protocol>://<host>:<port>/sap/bc/ui5_ui5/flmcg/ui5_inbox/index.html

·   <protocol>://<host>:<port>/sap/bc/ui5_ui5/flmcg/ui5_inbox_cloud/index.html

The first application uses the local (on premise) SAPUI5 libraries from your SAP system. The minimum supported version is 1.48. If the local SAP system does not have an up to date version of the SAPUI5 runtime, then the cloud version can be used.

 

Conversion activities:

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