The ARIS interface provides you with all the functions you need to connect ARIS with SAP® Solution Manager.
Depending on the required functional scope, the file sapjco3.jar must be provided on client computers and/or on ARIS Server. This connector is used to create the connection to the SAP® system using SAP® access parameters. For licensing reasons, it may not be installed automatically. The file sapjco3.jar is required for the following functions.
Synchronization (ARIS Server)
Run executable (client)
Show blueprint (client)
Show configuration (client)
Documentation (client)
For these client functions, a local SAP® GUI for Windows installation is required. For details see ARIS for SAP and SAP Requirements in the downloaded ARIS installation package, ARIS Download Center or Empower.
The following graphic shows the interaction of the individual systems and components when performing the above functions.
To use the Synchronization function, please make SAP® Java Connector available on the server. Furthermore, you need SAP® Solution Manager. For details, see ARIS for SAP® Solutions manual and ARIS Requirements for SAP® Solutions manual available in the ARIS Download Center or on Empower.
The Software AG RFC interface encapsulates the internal SAP API of SAP® Solution Manager. All calls via the interface use SAP-proprietary functions and functions used by SAP itself. This ensures that SAP changes are as transparent to the interface as possible.
If you use SAP® Solution Manager 7.2, transport requests are no longer required.
To ensure that SAP® synchronization between ARIS and SAP® Solution Manager 7.1 is available, your administrator must import the current transport request into the SAP® system.
You find the transport request in the ARIS installation package (.../Add-ons/Extension_pack_SAP/ABAP/Solution Manager/). The function modules are created in the /IDS/ARIS_SOLAR package in the /IDS/ARIS_SOLAR_001 function group.
The following graphic shows the interaction of the individual systems and components when performing the function Run customizing transaction/view (client).
The RFC interface to customizing is streamlined and consists only of one function module that enables you to call the view editing executable with the view specified in ARIS as a parameter.