SAP B1 IPO Executions Test

The integration framework provides standard ready-to-run scenarios, which can be changed and adopted for specific customer needs. In addition, the integration framework provides the possibility to create custom-specific scenarios to integrate and connect various software applications. In the integration framework, administrators work with scenario packages. The packages contain all relevant definitions to run the integration between applications.

The scenario packages are logistics units that can be activated or deactivated, exported and imported within different integration framework installations. A scenario package consists of one or multiple scenario steps. The scenario steps transfer and convert data from a sender to a receiver system. Each scenario step is a specific integration flow and has an inbound, a processing, and an outbound phase.

The scenario steps include the information which is required to perform the individual step. To perform a step some definitions are required such as how the step will be triggered, which system types communicate with each other, how the integration framework will transform the message, and if any other processing will occur, such as calls to external systems. Steps can be synchronous or asynchronous.

In an environment where integration framework plays a major role, it is essential to monitor the scenario steps that are performed/executed. If the steps take too long to execute or if the steps do not execute, the messages from the integration framework will not be transferred to the external systems. The SAP B1 IPO Executions test helps administrators keep a vigil on the execution of scenario steps.

This test auto-discovers the IPO URI of each Source (scenario package) and for each IPO URI reports the number of times the IPO URL was executed and the rate at which each IPO URI was executed. This test also helps administrators identify the IPO URI that took the maximum time for execution and also the average time taken by each IPO URI for execution. Using this test administrators can identify the IPO URI that is taking too long to execute.

Target of the test : A SAP Business One

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each Source: IPO URI on the target SAP Business One being monitored.

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured.
Port	Enter the port to which the specified host listens.
Database Type	By default, SAP Business One runs either on SAP HANA or Microsoft SQL Database server i.e., the backend database of SAP Business One is either SAP HANA or Microsoft SQL Database server. If the target SAP Business One runs on SAP HANA, choose HANA from the Database Type list. By default, MsSQL option will be chosen from this list indicating that the target SAP Business One runs on Microsoft SQL Database server.
Database Host	Specify the IP address of the host on which the database (i.e., the SAP HANA or Microsoft SQL Database server) of the target SAP Business One is installed.
Database Port	Specify the port at which the specified Database Host listens to. The default Database Port is 1433, if the target Business One runs on Microsoft SQL Database server and 30015, if the target Business One runs on SAP HANA.
Database User	If the target SAP Business One runs on Microsoft SQL Server 2005 or above, provide the name of a SQL user with all of the privileges outlined in User Privileges Required for Monitoring Microsoft SQL server in this text box. If the target SAP Business One runs on SAP HANA database server, then, a special database user account with Monitoring privileges has to be created on the SAP HANA database server of the target SAP Business One that requires monitoring. The syntax of the script that is used for user creation is discussed in Pre-requisites for Monitoring the SAP HANA Database Server. Specify the name of this user against the Database User parameter.
Password	Here, specify the password of the specified Database User.
Confirm Password	Confirm the password by retyping it here.
Database Name	To collect metrics from the logs of the target SAP Business One, the eG agent should connect to the SAP Business One database and other common databases such as RSP, B1if, SBO-COMMON etc. For this, you need to specify the name of the SAP Business One database corresponding to the target SAP Business One being monitored against the Database Name parameter. To know how to figure out the database name, refer to How to Find the Name of the SAP Business One Database?
Instance	This is set to default by default. This implies that the eG agent automatically discovers the instance name at run time.
Domain	This parameter is applicable only if MsSQL option is chosen from the Database Type list. By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the DOMAIN can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the DOMAIN text box, specify the Windows domain in which the managed Microsoft SQL server exists. Also, in such a case, the USER name and PASSWORD that you provide should be that of a user authorized to access the Microsoft SQL database server of the target SAP Business One.
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Executions	Indicates the number of times this IPO URI was executed during the last measurement period.	Number	Compare the value of this measure across IPO URIs to figure out the IPO URI that is executed more frequently.
Execution rate	Indicates the rate at which this IPO URI was executed during the last measurement period.	Executions/sec
Maximum response time of a step	Indicates the maximum time taken to execute an IPO step by this URI during the last measurement period.	Seconds	Compare the value of this measure across IPO URIs to figure out the IPO URI that took maximum time for execution.
Average response time of a step	Indicates the average time taken to execute an IPO step by this URI during the last measurement period.	Seconds/step