12
INITIAL AND BASIC CONFIGURATION OF SOLUTION MANAGER 7.01

Intial & Basic Configuration[1]

Embed Size (px)

DESCRIPTION

sap

Citation preview

Page 1: Intial & Basic Configuration[1]

INITIAL AND BASIC CONFIGURATIONOF

SOLUTION MANAGER 7.01

Page 2: Intial & Basic Configuration[1]

2

Table of Contents

Document Control

Page 3: Intial & Basic Configuration[1]

3

Version Date of Issue

Prepared byName Designation/Role-Department Email ID

Reviewed by

Approved by

Customer Approval

Document HistoryVersion No. Date of Issue Location of Change

Initial Document

This step creates an administration user for the ABAP and Java instances.1. Enter the User Data for the SAP Solution Manager Administration user.

Page 4: Intial & Basic Configuration[1]

4

The default user name is SOLMAN_ADMIN. You can accept this default or create a new user, with Create User.

The default administration role has all required authorizations. You can overwrite the default value according to your own naming convention. If you already have an administration user, you can adjust its authorizations, with "Update Authorizations Only".

If the activity is flagged as "Refresh" relevant, it means SAP updated the authorization template for administrator user. Enter the existing username and select "Update Authorizations Only".

2. Choose Execute.

This step should be run once. The system performs the following basic configuration: Log SAP Solution Manager on to the system administration Create logical systems for the SAP Solution Manager Activate the Service Data Control Center (SDCCN)

Choose Execute.

This step configures: J2EE & SLD Connect JAVA and SAP Solution Manager ABAP with CTC script (Central Technical

Configuration script) Technical user

1. Choose Start Configuration. Close all open browser windows before you start the J2EE & SLD configuration, to ensure that existing logon data is not reused.

2. The system opens a logon dialog, in which you enter the administration user (e.g. SOLMAN_ADMIN)Enter the user for the ABAP instance (default value: SOLMAN_ADMIN) and the Java instance (default value: J2EE_ADMIN) and their passwords, in the following screen. Note: You can also use SOLMAN_ADMIN for the Java instance.

3. Choose Continue. The system starts a configuration script. You can display a hierarchical overview of the

Page 5: Intial & Basic Configuration[1]

5

configuration activities, with their status, with the symbol with the Quick Info Log. If the configuration script ends with a success message, close the screen.

4. To transfer the system data from SLD into the system landscape, choose Read SLD. The system starts a background job. The system shows whether the background job has been scheduled, in the initial screen, under log.

BASIC CONFIGURATIONCreate the SAP Solution Manager configuration Project. The system saves all configuration status information in the project, so you can only create one configuration project.

1. Enter the required data. SAP Solution Manager puts all production systems in your landscape that are known and

connected to system administration, in the Solution. This ensures, for example, that you can Deliver Services to all production systems.

The default Leading Role is "P" (Production). If you have defined your own role for your production system, enter it here.

The Logical Component “Z_SOLMAN_COMP" is created for the Solution Manager. The default Project Language is the logon language.

2. Choose Create.      The system shows related messages in the Log screen area.

Page 6: Intial & Basic Configuration[1]

6

Read and import the central correction note (CCN) 1468591 into your system with Download. Caution: This note contains automatic and manual corrections. Read the note and perform all manual actions in section 2 "Corrections with manual steps"

To implement this note, choose SAP Note Assistant. The system starts the transaction SNOTE, imports all notes in the CCN, as far as possible, automatically, and informs you about any manual activities required.You tell the system manually in a Status, whether you have implemented the note. If so, set the status to "Performed".You can have the system perform other manual steps in the notes, automatically, e.g. starting clean-up reports in the function Post-Processing.

This is an automatic installation check for configuration-relevant parts of the installation. Each check is documented in detail.

To display information for a check, click on Display, under Automatic Activities, in the IMG Documentation column.

Choose Execute All to perform all checks. Choose Execute Selected to only perform the activity selected in the table.

To perform the check manually, click on the button in the Navigation column, if there is one.

Page 7: Intial & Basic Configuration[1]

7

You can log the manual activity, and deactivate an automatic activity, in the Execution Status column.

1. Get the logon data for the S user and the system administration.

The SAP backend S user communicates between SAP Solution Manager and the support infrastructure in the SAP backend system.

The S user for the current user gives the logged on user access to his data and information.

The system needs the system administration logon data for further configuration.

2. You can also influence the configuration of the SAP BW system used, under Provide BW Configuration Information. In a new installation or an upgrade, the BW system is activated in client 001 by default. To change this, perform a client copy before you continue with the configuration (see IMG under "Set-Up BW client").

3. To save the entries made on 1. & 2. and to make the connection to SAP Service Marketplace (RFC connections SAP-OSS and SAP-OSS-LIST-O01), choose Maintain Connections.

4. The system creates several default users in the automatic configuration, according to the data you enter under Provide User Information, and assigns the required roles to them automatically. The system creates the password of the proposed user automatically, by default.

The system user communicates for services in the Internet Communication Framework (ICF).

The batch user schedules steps for background processing. The SAP support user authorizes Active Global Support to provide support in the SAP

Solution Manager system. Enter the password for this user manually.5. Choose Maintain Users to perform this basic configuration step.

Page 8: Intial & Basic Configuration[1]

8

Enter information about your system landscape, under Wily Introscope Enterprise Manager. This data is obligatory for Solution Manager Diagnostics, to analyze the status of Java systems, e.g. performance data.1. Enter one row per system. The system connects this analysis tool to the SAP Solution Manager,

in automatic configuration. You can adjust this connection later, in Solution Manager Diagnostics (under Administration).

2. You can specify automatic update of the table SAPRouter. The system automatically updates all required entries in the saprouttab , when you open a service connection. Select a row. The system displays detailed information about the selected entry, under the list. You can change it. Enter the required data, for example, set the checkbox Active for automatic update of the route permission table, and choose Check Data. The system saves your entries.

Manual configuration activities are required.1. If the activity to be performed is documented in the IMG, you can display the documentation

with Display in the IMG Documentation column, under Manual Activities.2. To perform an activity, click on it in the Navigation column, if there is one.

Page 9: Intial & Basic Configuration[1]

9

3. When the activity has been performed, change the Execution Status in the Execution Status column, to “Performed”, and choose Save.

SAP Solution Manager performs the following activities in automatic configuration. You can exclude activities from automatic performance.1. Set the Postponed flag in the Execution Status column, for activities which the system

should not yet perform. The system only automatically configures entries with the execution status Execute.

2. To start automatic configuration, choose Execute ALL. Note: Automatic configuration can take a few minutes. As the activities run in a background process, you must choose Refresh to update the logs. The dynamically displayed asynchronous execution status table shows the progress of the background process.

3. After configuration, you can see messages and other detailed information for a selected automatic activity, in the Log screen area.

4. If you automatically configure again, you can specify in a dialog window whether the system should repeat activities that have already been performed.

5. For more information about performing activities manually, click on Display in the IMG Documentation column.

6. To perform activities manually, set the Execution Status to Manual, go to the activity via the Navigation column, and edit it.

Page 10: Intial & Basic Configuration[1]

10

Basic configuration is completed successful.Start Managed System Configuration.