TBOM creation from SAP TAO
You want to know all prerequisites to TBOM creation or may be
facing issues with TBOM creation in SAP TAO.
Prerequisites for TBOM creation in SAP TAO. RFC Connections
and the two possible scenarios will be covered.
In order for TBOMs to be created correctly either through SAP TAO
or even through SOLAR01 directly, there are several authorizations that are
needed on both your Solution Manager and Satellite systems.
There are two possible User ID combinations:
Scenario 1
In Solution Manager you have a "User ID A". On the
Satellite system "User ID A" is available and will be used for
execution. All tests from SAP TAO will be used by "User ID A"
Scenario 2
In Solution Manger you have a "User ID A". On the
satellite system "User ID A" exists; however "User ID B" is
used for all test executions. ALl tests from SAP TAO will be used by
"User ID B"
In the next sessions you can see which authorizations are required
depending on the above mentioned situation.
Scenario 1
SAP Solution Manager Authorizations required for User A:
- Required Role in order to
display Business Blueprint Structure of a solution manager project:
SAP_SOL_PROJ_ADMIN_DIS
- Required Role in order to
create / modify TBOMs: SAP_SM_BPCA_TBOM_ALL
- Required Role in order to
start/ stop trace recording on the managed SAP system, and to subsequently
collect the trace information for TBOM creation: SAP_S_RFCACL
Satellite system authorizations required for User A:
- Required Role in order to
be able to start/ stop trace recording on the managed SAP system, and to
subsequently collect the trace information for TBOM creation: SAP_S_RFCACL
- User A should be able to
process business transaction on the managed system
SAP Solution Manager Authorizations required for User A:
- Required Role in order to
display Business Blueprint Structure of a solution manager project:
SAP_SOL_PROJ_ADMIN_DIS
- Required Role in order to
create / modify TBOMs: SAP_SM_BPCA_TBOM_ALL
- Required Role in order to
start/ stop trace recording on the managed SAP system, and to subsequently
collect the trace information for TBOM creation: SAP_S_RFCACL
Satellite System authorizations required for User A:
- Required Role in order to
be able to start/ stop trace recording on the managed SAP system, and to
subsequently collect the trace information for TBOM creation: SAP_S_RFCACL
Satellite System authorizations required for User B:
- User B should be able to
process business transaction on the managed system
Authorizations for executing the business scenario(s)
- In case 1: User A needs
should able to process the business scenario(s)
- In case 2: User B needs
should to process the business scenario(s). (Note: User B does not need to
have RFC authorizations)
A trusted RFC connection must be available in both directions
between the SAP Solution Manager and the Managed Systems for TBOM Creation.
This helps in switching on/off the traces which are required for this purpose.
In order to verify the existence of an appropriate trusted RFC
connection, process transaction SM59. You will be shown a similar screen as the
following one:
In the logon tab the setting should be set to the current user, so any user given in SAP TAO for SAP Solution Manager connection is valid.
Confirm that this connection is working by clicking on the
"Remove Logon" from the Solution Manager system to the Satellite
system. Subsequently, execute the “Remote Logon” in order to log on to the corresponding
Managed System. From Managed system, also try to logon to SAP Solution Manager
using this trusted RFC connection.
Note that in the managed system both Back and Trusted connections
should be present, as per screenshot below:
The entry for the Managed System in SAP Logon must appropriately
provide the Message Server Host as this is needed in order to determine the
actual Managed System. Please see this screenshot showing 4 valid entries
and 1 invalid entry (last line outlined in blue):
The message server host together with the short SID helps
composing a unique key for determining the target ABAP system. SAP TAO will
first use “Message Server” property, but if it is not provided, then it would
try to use the “Group/Server” entry. The fall back to “Group/Server” will work
only if the Application server and message are on the same host.
The TBOM creation functionality has to be enabled from
Configuration-> Run and Report tab. This way the user can switch off the
TBOM creation functionality when it’s not required to improve SAP TAO
performance.
For Online Class contact:
Your idea of increasing the automation coverage is good. It could help with sap upgrade automation too. But it could also be too complicated.
ReplyDelete