Skip to end of metadata
Go to start of metadata
A manual activity is an activity that the user of the guided procedure has to carry out in the managed system. It cannot be automated. Nevertheless you can provide user with a navigation link to open the transaction, URL or report which is used to perform the manual activity. 

  You can add manual activities to steps of type "Manual", "Mixed - Auto & Manual " or "Mixed - Custom & Manual " . Each step can contain multiple manual activities.

  1. Select "New" to add a new activity and enter an activity description.
  2. Select Type "Simple".
  3. Select "New" to define a navigation link. The navigation link definition UI opens.

 

  1. Select the target of the navigation link. Possible values are "Solution Manager System", "Managed  System" or "Others" . IF you choose "Solution Manager", the  link will point to the solution manager system. If you choose "Managed System", the  link will point to the managed system for which the current  step is being executed. by chooseing others you can enter any  static URL as navigation link or a  navigation link to a specific SAP Note in the SAP Support Portal.
  2. Select and parametrize the  URL Type that fits to your requirements. 
    The URL types that are used most often are explained below:
     
  3. You can  use  variables in the URL to pass variable  information like  managed system, database or host to the called application. How to do this is explained here: 
  • TRANS_SM  - ABAP transaction on Solution Manager system
  • TRANS_ST  - ABAP transaction on managed system

Navigation link to an ABAP transaction in Solution Manager or in the managed ABAP system via SAPGUI for HTML (ITS webgui)

You need to define a manual activity with a navigation link to a  ABAP transaction in an ABAP system.  SAPgui shall not be used.

Enter the transaction name . You can optionally pass addtional variables and ok-codes as shown in the example below.

  • Webgui service on managed system or on Solution Manager has been activated (transaction SICF --> /default_host/sap/bc/gui/sap/its/)
  • The load balancer host and port of the managed system / Solution Manager has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".
  • The ABAP client that should be called  has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".
  • How to define a navigation link that calls transaction SXMB_ADM in the managed ABAP system is shown below:

  • How to define a navigation link that immediately executes an ABAP report in SAPGui for HTML is shown below. It performs the following:
    Call transaction SE38 in Solution Manager, pass report name "SHOWCOLO" and trigger the execution of this report.
  • SAPGUI_SM  - ABAP transaction on Solution Manager system (SAPGUI for Win)
  • SAPGUI_ST  - ABAP transaction on managed system (SAPGUI for Win)

Navigation link to an ABAP transaction in Solution Manager or in the managed ABAP system via SAPGUI. When the link is being selected ,a SAPGui short cut will be generated temporarily and executed automatically (depending on the browser settings. 

You need to define a manual activity with a navigation link to a  ABAP transaction in an ABAP system. ITS shall not be used.

Enter the transaction name . You can optionally pass addtional variables and ok codes as shown in the example below.

  • SAP Gui client is installed locally on all desktops of the guided procedure processors.
  • The ABAP client that should be called  has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".

How to define a navigation link that immediately executes an ABAP report in SAPGui is shown below. It performs the following:
Call transaction SE38 in managed system, pass report name "SHOWCOLO" and trigger the execution of this report.

The SAPGui navigation links will prompt by default for user and password even if SSO via SNC was activated. If SSO should be used, please refer to SAP Note 2040347

  • WD_ABAP_SM  - ABAP Web Dynpro URL on Solution Manager System
  • WD_ABAP_ST  - ABAP Web Dynpro URL on managed system

Navigation link to a web dynpro  application in Solution Manager or in the managed ABAP system. When the link is being selected ,a SAPGui short cut will be generated temporarily and executed automatically (depending on the browser settings.

You need to define a manual activity with a navigation link to a  Web Dynpro application in an ABAP system. 

Enter the path to the Web Dynpro application . Specify additional URL parameters if required as shown below.

  • The load balancer host and port of the managed system / Solution Manager has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".
  • The ABAP client that should be called  has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".

How to define a navigation link that opens the technical monitoring web dynpro application in Solution Manager is shown below:

 

  • SERVLET_SM - Servlet on Solution Manager System (Java Stack)
  • SERVLET_ST - Servlet on managed Java system

Navigation link to a servlet in Solution Manager Java stack or in the managed Java system. When the link is being selected ,a SAPGui short cut will be generated temporarily and executed automatically (depending on the browser settings.

You need to define a manual activity with a navigation link to a servlet in a JAVA system.

Enter the path to the servlet . Specify additional URL parameters if required.

  • The load balancer host and port of the managed system / Solution Manager has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".

How to define a navigation link that opens the system info page in a Java system is shown below:

  • WD_JAVA_SM - Web Dynpro URL on Solution Manager System (Java Stack)
  • WD_JAVA_ST - Web Dynpro URL on managed Java system

Navigation link to a web dynpro application in Solution Manager Java stack or in the managed Java system.

You need to define a manual activity with a navigation link to a Web Dynpro application in a JAVA system.

Enter the path to the Web Dynpro application . Specify additional URL parameters if required.

The load balancer host and port of the managed system / Solution Manager has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".

How to define a navigation link that opens the Netweaver Administrator in a Java system is shown below:

 

Extern_ST - External Application on Managed System

Navigation link to an application in any managed system which is accessible via an URL.

You need to define a manual activity with a navigation link to an application or page in non ABAP and non Java managed systems. 

Enter the path to the application or page.

The load balancer host and port of the managed system has been entered in the SAP Solution Manager Configuration Work Center --> Managed Systems Configuration --> Step "Enter System Parameters".

How to define a navigation link that opens the Central Management Console in a SAP BusinessObjects System is shown below:

How to use dynamic values in navigation links

In some cases you need to pass some dynamic content like the system id of the managed system or the database id or current date in the URL.

You can use predefined variables for this purpose. The variables are replaced by dynamic values during runtime.

The following dynamic variables are supported:

VariableDescriptionRemark

T_SYSTEM_ID

System id and system type (e.g. PRD~ABAP)Can be used only if the scope of the guided procedure or step is a technical system.
T_SYSTEM_INSTALL_NUMBERInstallation Number of the managed systemCan be used only if the scope of the guided procedure or step is a technical system of type ABAP or JAVA.
 T_SYSTEM_LONG_SIDLong system id of the managed system (e.g. PRD00001)Can be used only if the scope of the guided procedure or step is a technical system.
 T_SYSTEM_PRODCLNT Productive client of the managed system as defined in managed system configurationCan be used only if the scope of the guided procedure or step is a technical system of type ABAP.
 T_SYSTEM_SID

System id of the managed system (e.g. PRD)

Can be used only if the scope of the guided procedure or step is a technical system.
 T_SYSTEM_TYPE Type of the managed system (e.g. ABAP, JAVA)

Can be used only if the scope of the guided procedure or step is a technical system.

 DBMS_ID Database ID (e.g. PRD)Can be used only if the scope of the guided procedure or step is a database.
 DBMS_VENDOR Database vendor (e.g. SAP) Can be used only if the scope of the guided procedure or step is a database.
 DBMS_RELEASE Reelase of the database (e.g. 1.00.51.0374591) Can be used only if the scope of the guided procedure or step is a database.
 DB_SYSTEM_ID Database ID (e.g. PRD) Can be used only if the scope of the guided procedure or step is SAP HANA database.
 HOST_FULL_NAME  full qualified host name (e.g. prdci.wdf.sap.corp) Can be used only if the scope of the guided procedure or step is a host.
 HOST_ID  host name (e.g. prdci) Can be used only if the scope of the guided procedure or step is a host.
 HOST_IP  IP address of the host Can be used only if the scope of the guided procedure or step is a host.

Up to Solution Manager 7.1 SP12 other  dynamic variables can be selected which have no function in the guided procedure execution context. As of  Solution Manager 7.1 SP13 these variables will not be shown any more. Please use in your guided procedures only the variables listed above.

You can find below  some examples how to navigate context sensitively to different Solution Manager applications and use  dynamic variables in navigation links:

During runtime the variable T_SYSTEM_ID will be replaced dynamically with the system id of the managed system for which the guided procedure or step is being executed.

 

 

During runtime the variable DBMS_ID will be replaced dynamically with the database id  for which the guided procedure or step is being executed.

 

During runtime the variable HOST_NAME will be replaced dynamically with the host name for which the guided procedure or step is being executed.

In the examples above, the parameter APP_ID determines the solution manager application to be called. You can find a list of all available application ids in the Solution Manager Administration Work Center --> Infrastructure --> Content --> URL Framework.

 

 

  • No labels