setup solution manager

7/27/2019 Setup Solution Manager

1/26

Solution Manager - Customer System Configuration for Solution Manager

22 February 2006 Page1/26

Solution Manager

Customer System Configurationfor Solution Manager

Version: 1.8Author: Andreas da Trindade(originally: Warren Chirhart)


2/26


Index / Quick checklist

1 Integrating a customer system with Solution Manager............................................3

1.1 Required IT/IBC ticket for connectivity......................................................................31.2 Things to do in the customer system............................................................................3

1.2.1 Required Plug-ins.....................................................................................................................3

1.2.2 Required roles for use of new Service Data Control Center....................................................4

1.2.3 Activating the new Service Data Control Center.....................................................................4

1.3 Things to do in SOL......................................................................................................91.3.1 Creating a Customer Solution..................................................................................................9

1.3.2 Creating customer systems and components..........................................................................10

2 Changes and Removals in Solution Manager.........................................................18

2.1 Post-system copy procedures for customer system...................................................18

2.2 Changing System information for an existing instance............................................21

2.3 Disabling Early Watch reports for a customer system.............................................21

2.4 Removing a system from a customer solution...........................................................22

3 Troubleshooting.......................................................................................................24

3.1 RFC Destination problems.........................................................................................243.1.1 Route permission denied .......................................................................................................24

3.1.2 Error opening RFC connection or similar message................................................................243.1.3 SDCC_OSS cannot be created...............................................................................................24

3.2 Problems in SMSY......................................................................................................253.2.1 System/Object X already exists. . ..........................................................................................25



3/26


1 Integrating a customer system with SolutionManager

This chapter explains the steps to add a new customer system to the SolutionManager.

1.1 Required IT/IBC ticket for connectivityWhile installing the system, it would be a good idea to open an IT/IBC ticket to theSR-NETWORK-EXT_DC group requesting that the required ports be opened fromthe customer system to the Solution Manager. The request should be formattedsimilar to the following:

Please open the following ports for communication with the new Solution Manager system(hg10761):

hg10761 (203.13.155.122) (IP_address), port 33xx hg10761, port 3301 (via saproute /H/203.13.155.17/S/3299/H/hg10761)

where xx is the instance number of the customer system. The saproute informationis important so that the networking group can test the connection properly afteropening the ports.

1.2 Things to do in the customer system

1.2.1 Required Plug-ins

For a customer system to work properly with the new Solution Manager system, thenewest support plug-ins must be installed using SAINT. These plug-ins can bedownloaded from the SAP Service Marketplace under Installations and Upgrades

Plug-Ins SAP Solution Tools and Support Packages and Patches Plug-Ins SAP Solution Tools for the Support Packages of the plug-ins.ST-PI (2005_1_), for example: 2005_1_640ST-A/PI (01F_), for example: 01F_BCO640

ST-PI requires at least Support Package 1 to prevent a problem with thegeneration of Early Watch reports. OSS Notes 539977 and 69455 provide additional

information about these plug-ins.

https://websmp201.sap-ag.de/~sapidb/012006153200001581432002E.ITFhttps://websmp201.sap-ag.de/~sapidb/011000358700009172762001E.ITFhttps://websmp201.sap-ag.de/~sapidb/012006153200001581432002E.ITFhttps://websmp201.sap-ag.de/~sapidb/011000358700009172762001E.ITF


4/26


1.2.2 Required roles for use of new Service Data Control Center

With the application of the new plug-ins, the SDCC transaction is no longer used. Ithas been replaced by the SDCCN transaction. In order to use this transaction,additional roles may be needed. If you experience problems working with SDCCN in

the customer system, assign the following roles if the system is release 610 andlater:

SAP_SDCCN_ALL (Administrative, change setup)SAP_SDCCN_DIS (Display only)SAP_SDCCN_EXE (Maintain)

In earlier releases, the following profiles may be used:

S_SDCC_ADM_N (Administration)S_SDCC_READN (Display)S_SDCC_SERVN (Collect and send data)

1.2.3 Activating the new Service Data Control Center

To activate the Service Data Control Center from the local system:

1. Call the Service Data Control Center (transaction SDCCN).

2. Choose Utilities Activate

3. ConfirmYes to activate on local system

4. You are prompted to set up a new RFC destination to the SAP Service systemthat will be used by the Service Data Control Center. ClickYes.



5/26


5. Confirm. If you receive an error while creating the SDCC_OSS, see thetroubleshooting section at the end of this document.

6. Confirm the two tasks that are created.

7. A screen appears confirming the activation and scheduling of the MaintenanceTask

The Service Data Control Center is now activated. You must next ensure that theSAP Solution Manager system is made known to the Service Data Control Center inthe local system.

8. In the Service Data Control Center, choose Goto Settings Task-specificandselect Settings

9. Select the View RFC Destinations button



6/26


10. Create the SOLUTION_MANAGER destination with the following settings

Connection Type: 3Target Host: /H/203.13.155.17/S/3299/H/solmanSystem number: 01Client: 000User: RZ20USERPassword: 1derland

Save and perform a Test Connection. If there is a failure, refer to theTroubleshooting section at the end of this document.

11. Click the back button two or three times to return to the previous SDCCN (RFCDestinations) screen

12. Select the Change button followed by the Add RFC Destination button

13. Create an entry for the SOLUTION_MANAGER destination and Continue

14. Click and thenYes to save entries.

15. Run Service Preparation Tool from the tasks list and perform whatever additionalsteps are required. Note the selection for the Solution Manager system in the

following screen:



7/26


For BW systems, the following warning appears in the results list of the ServicePreparation Check. Notify the customer that the steps below should be carried out inthe BW working client

Confirm the task is completed when prompted

16. Schedule an Early Watch session to be sent to the SDCC_OSS destination(SAP) by performing the following steps:

Click the Create task button



8/26


Select the Request session data task

Select the Periodic radio button and the EarlyWatch Alert report

Set the scheduled date for the next Monday on the calendar and 04:15 for the time.The SAP RFC Destination should be SDCC_OSS

A confirmation dialog will confirm that the task has been scheduled

The following task should now be found in the To do list ofSDCCN on the customersystem (the session number will vary)



9/26


1.3 Things to do in SOL

1.3.1 Creating a Customer Solution

1. Logon to SOL, client 000

The Solution only has to be defined once. Ifthe customers solution already exists,skip to section 1.3.2.

2. Execute transaction SOLUTION_MANAGER

3. Click on the New button

4. Fill in the required information and click Continue, example given below:

5. In the resulting screen, click the System Maintenance icon, which opens thescreen for transaction SMSY



10/26


1.3.2 Creating customer systems and components

The following steps are carried out using transaction SMSY. If section 1.3.1 has justbeen carried out completely, then the current screen is the correct starting place.Otherwise, go to transaction SMSY.

1. Under Landscape Components, right-click on Server, choose Create New Server

2. Enter the server hostname and click the Save button

3. Enter as much information as is available (check in SISM) for this server

4. On the Header Data tab, enter the hostname in the Description field and Save

Repeat steps 2 through 4 for each server that is part of the system (DB server, appservers, ITS, etc)



11/26


5. Right click on Database and choose Create New Database

6. Enter the SID of the database and click Save. If the database SID already exists,add a number to the end, for example: AHQ0

7. Enter all available information, assign the appropriate server and Save

8. Right click on Systems and choose Create New System

9. Enter the SID, product information and Save. If the SID already existsfor anothercustomer, add a number to the end, for example AHQ0. Even though Solution

Manager will complain about this, click the button. The SID will be saved.

Officially, the SID used here can be between 3 and 6 characters long.



12/26


10. Confirm component and enter SID in Description field, then Save. If the relevantflag is changed, a message will appear warning of possible data loss. Continue.

11. Drill down to the new product for the system and select it

12. Fill in the required info



13/26


13. Click the Clients tab and fill in the first row with only the minimal amount of dataneeded, as shown below

14. Click on the Generate RFC button and fill out the resulting screen asshown



14/26


15. Click the Generate RFC Connections button at the bottom of the screen.The following window appears. If all lights are green, the RFC connection has beengenerated on the customer system and the remaining data in the previous screenhas been filled in. If an error occurred, it is probable that there is still an issue withthe ports.

Example results of a successful connection:



15/26


IMPORTANT

Skip to step 18 to add a new system if the required logical component for thiscustomers landscape/product has already been created. Steps 16 and 17 are onlynecessary if this is the first of the customers systems for this particular landscape.

Each landscape (BW, Enterprise, CRM, R/3 4.x, etc) will have a unique LogicalComponent. These logical components only allow entries for one of each type of R/3system (DEV, QAS, PRD, SBX, etc). See step 20 for a screen shot of this.

16. Go to the System Groups and Logical Components bar. Right-click onLogical Components and select Create New Logical Components

17. Create a Logical Component for the customer and click Continue.

18. Correct the Product Version, if needed, and assign known System:Clients totheir appropriate roles using the drop-down.

If a new customer system is simply being added to an existing logical component,then after completing this task, proceed to step 23.



16/26


19. Expand the Solution Landscapes group and select the customer solution

20. Select the drop-down for the Logical Component field

21. Find and select the Logical Component created in steps 16 through 18. ClickOK to save.

22. The customers information is automatically updated here. Repeat these stepsfor any additional landscapes implemented (EP, SAP R/3, Web AS, etc)



17/26


23. Right-click on each system and choose Put in Solution

When complete, the systems will be shaded green

24. Save changes. The customer systems are now integrated into the Solution

Manager system.



18/26


2 Changes and Removals in Solution Manager

2.1 Post-system copy procedures for customer systemTwo scenarios exist for this topic. The first scenario addresses a system copy fromone existing instance to another, such as with a copy of Production to QualityAssurance, for instance. This scenario also assumes that both systems are alreadyconfigured in the Solution Manager, as covered in the previous section. The secondscenario is the copy/migration of an existing system to new hardware.

Only for system copy/migration to new hardware:1. Log into Solution Manager System, SOL2. Execute transaction SM593. Modify the SM_CLNT_READ entry under R/3 Connections,

so that the entry reflects the correct customer system information4. Create the new server name in transaction SMSY, as described in Section

1.3.2, steps 1 through 45. Go to Landscape Components Systems and select the appropriatesystem component, as shown below

6. Click the change button on the toolbar7. In the right-hand pane, click the Read System Data Remote button8. Once the system data read has been completed, confirm that the information

now reflects the new system data9. Finished!



19/26


Only for system copy to an existing instance:1. Log into the customer system, client 000, as DDIC2. Execute transaction SDCCN and select the To do tab

3. Delete all scheduled tasks.4. In a separate SAPGUI session, go to transaction SM37 and search for any

/BDL/TASK_PROCESSOR jobs, which are scheduled or released, anddelete them

5. In SDCCN, create new Maintenance Package and Service Preparation

Check tasks, using the button. When creating these tasks, click thebutton in order to schedule these jobs as periodic (default is Run once). TheMaintenance Package will run once a day. The Service Preparation checkwill be every 30 days.

6. From the menu bar, select Goto Settings Task Processorand confirmthat the Job scheduling status is Active, and that the Job frequency isHourly, as shown below

This screen describes the behavior of the/BDL/TASK_PROCESSOR job.



20/26


7. Create a new Refresh Sessions task, scheduled to run Now, useSOLUTION_MANAGER as the Target RFC Destination and execute using

the button

8. Confirm that Early Watch sessions scheduled in Solution Manager for thecustomer system appear in the To do list of the customer system once theRefresh Sessions task has completed.

9. If the customer has their own Solution Manager system, perform step 7 and 8again using the RFC destination for their Solution Manager system.

10. Schedule an Early Watch Alert to be sent to SAP OSS, as detailed in Chapter1.2.3, step 16.

11. Finished!



21/26


2.2 Changing System information for an existing instanceIf changes have been made to an instance, these changes will be recognizedautomatically by Solution Manager. However, in order for this to happen, the RFCdestination used by the Solution Manager must be correct. See the above section,

2.1, for information on updating the RFC connection.

If nothing has been changed with the central instance, then no changes need to bemade manually to the entries in Solution Manager. The Solution Manager willautomatically collect information regarding the customer systems DB, new dialoginstances, plug-ins, etc.

2.3 Disabling Early Watch reports for a customer systemEarly Watch reports are no longer needed or wanted for a particular customer system

1. Log into Solution Manager System, SOL

2. Execute transaction SOLUTION_MANAGER3. Click on the appropriate customer solution from the list4. In the left-hand pane click on Operations Setup, if not already selected5. In the right-hand pane, select Solution Landscape Maintenance6. Click on the tab labeled Solution Settings7. Click on the button labeled Setup EWA8. Clear the check-box under the Select column for the instance which should

no longer generate Early Watch reports

9. Click the button and exit from the transaction



22/26


2.4 Removing a system from a customer solutionIf a customer system is no longer being used, is retired, etc, then that system can becompletely removed from the customers solution. Please be advised that thisprocedure will remove all past Early Watch reports for this system from the Solution

Manager database. These cannot be recovered.

1. Log into Solution Manager System, SOL2. Execute transaction SMSY3. Go to the System Groups and Logical Components, on the left of the screen,

and select the Solution Landscape corresponding to the customer

4. Find which Logical Component and Product [Main Instance] the retired-

system belongs to. In the example below, these values, for system DPW,would be ZDUPONT NW40 BW35 and SAP NETWEAVER [BI]

5. Click on the button on the SAPGUI toolbar6. Right-click on the system which is to be remove from the solution

7. Select Remove from Solution and click the button

8. On the left-hand side of the screen, navigate to Logical Components and

down to the entry for the Product (i.e. SAP NETWEAVER BI) and find thecustomers Logical Component (i.e. ZDUPONT NW40 BW35)



23/26


9. Click on the button on the SAPGUI toolbar10. On the right-hand side of the screen, select the drop-down for the system to

be deleted

11. Scroll to the top of the resulting list, select the blank entry and click on thebutton

12. Click on the button to save. The Solution Landscape should automaticallybe refreshed so that this system is no longer displayed.

If the system is to be completely removed from the Solution Manager, all systemrelated components can be deleted from the Landscape Components section on the

left-hand side of the screen. Execute (Where-used) before deleting eachcomponent, to ensure it is not used elsewhere. Start with the components underSystems, followed by Databases, followed by Server.



24/26


3 Troubleshooting

3.1 RFC Destination problems

3.1.1 Route permission deniedThis is due to the saprouter and an email should be sent to Jochen Diehl asking foryour customer host systems to be added to the saprouttab. Provide the connectioninformation, for example:

IP_cust_host communicating on port 3301 using saproute/H/203.13.155.17/S/3299/H/203.13.155.122

3.1.2 Error opening RFC connection or similar message

Most likely this is due to a port not being opened. Confirm this first by trying thefollowing:

1. Check all settings in the

1. Replace all hostnames with IP addresses in the target host field of the RFCdestination and perform a test connection. If this works, then use this information forthe RFC and open a ticket to SH-NETSEC notifying them that the DNS is not workingproperly for the customer system.

2. Change the target host field to point to the old Solution Manager system andconfirm that this connection works:

/H/203.13.155.17/S/3299/H/droth992, port 3300

If this works, then open another ticket (or reopen the original ticket) to SH-NETSECand request the ports be opened as mentioned at the beginning of this document.

Additional testing can be done using NIPING.

3.1.3 SDCC_OSS cannot be created

The SDCC_OSS connection is created from a copy of the destination SAPOSS.Therefore the SAPOSS destination must be working correctly before this connectioncan be created. If SAPOSS is not working, check your entries. If everything iscorrect, open a SH-NETSEC message requesting the ports needed.

Once the SAPOSS connection is working properly, the SDCC_OSS connection canbe generated using the following steps:

1. In the Service Data Control Center, choose Goto Settings Task-specificandselect Settings

2. Select the Create Destination to SAPNet R/3 Frontend button



25/26


3. The following screen appears

3.2 Problems in SMSY

3.2.1 System/Object X already exists. . .

If this error occurs, the object which is being created already exists in the systemlandscape information.

1. To find the system, from transaction SMSY, go to Utilities -> Analyses

2. Execute the report with the object or system name inserted into the appropriatefield. The report can also be run without any entries, but all objects will be displayed

3. A list is created of all the objects matching your request



26/26


Clicking on an object in the list will bring you to its entry in SMSY. From there, it canbe determined if this entry is for your system (another colleague already entered theinfo, for example) or perhaps another customer system exists with the same SID.

If the system has no product assigned, you will be prompted to either delete the entryor assign a product. If you assign a product, follow the steps in section 1.3.2, startingwith step 12. However, it is most times easier to choose Delete and re-enter thesystem information, as described starting from section 1.3.2, step 9.

setup solution manager

Documents