System components support non-ABAP main instances in the system landscape maintenance. A system component is always assigned to a type, e.g. J2EE or TREX, to identify its task or underlying technology.
A system component can belong to different systems. In the SAP Solution Manager, you capture the data for a system component once, independently of a system. Then assign the system component to the systems which use it. There are the following types of system components. SAP can specify more.
ITS
Java System
TREX
Procedure
Create system component
Note
You can create system components manually. Some types can also be copied automatically from a connected System Landscape Directory (SLD).
Choose
in the overview tree.Choose Create New System Component from the context menu.
Enter a name.
Choose a type.
Save your changes.
Enter the required data in the right-hand side of the screen, in the Header Data and Instances tabs.
In the Software Components tab, you can:
Select installed software components from the possible entries help.
Copy software components from a main instance of a product with From Main Instance.
Specify software component patch level.
You can enter values for the attributes you defined, in the Attributes tab.
Save your changes.
Assign system component to a system
Note
System components are not automatically linked to a system. To specify that a system component takes the role of a main instance of a system, you must explicitly assign the system component to this main instance. You perform this step manually.
Choose
-> Main Instance Selection tab, in the overview tree.Set the System Component Assignment flag for the relevant main instances.
Choose the system component from the possible entries help.
Note
Information which you had previously captured for the main instance is discarded, i.e. wherever the Solution Manager gets data for the main instance, it gets it from the assigned system component. The system component replaces the information directly at the main instance.
End of the note.Recommendation
Create, for example, a TREX centrally as a system component and assign it to the main instances of the systems in which it is to be used.
You can assign further system components to a relevant main instance.
Note
There are main instances in SAP product definitions which cannot be classified, i.e. they are based on various technologies or perform various tasks. In this case, you can assign other system components to a relevant main instance. This extended assignment of system components to a main instance depends upon whether a system component is already assigned to the main instance.
End of the note.Save your changes.
1 comment:
For a Excellent Online Resource for SAP EP and SAP Web Dynpro ABAP, Visit Learn SAP Online
SAP EP - Standard Portal Services
Portal Eventing and Navigation
Portal Look and Feel - Branding the Portal
How to Develop Portal Applications
SAP EP-Developing portal content and assigning permissions
SAP EP-Role maintenance
SAP EP-How to make Enterprise Portal highly available
Implement Single Sign On
SAP EP-J2EE architechture
What is SAP Enterprise Portal
And Many More...
Basics of Web Dynpro ABAP
ABAP Data Types and Objects
ABAP Statements
WD4A - Introduction WDA - SAP Logon Procedures
WD4A-Format the Values appearing on value Axis of Business Graphic
WD4A-Navigate from one view to another and back to previous view
WD4A - How to Calculate next 12 months from current month in web dynpro ABAP
WD4A - Validate Inputs in a web dynpro ABAP Application
And Many More...
Post a Comment