Solution Manager 7.2 Configuration hint

Before start the configuration, please take the ABAP and JAVA export to build DEV or Quality system.

*************************************************************************************

Key point: System preparation

1.Define System role:

Development or quality or production or Demo system. If you mentioned in LMDB it will fetch automatically otherwise you must specify.

User roles are not copied automatically. So you should enable it by using table PRGN_CUST sap note 1723881.

“After you implement these corrections, you have the option to apply the setting for changes and transports of client-dependent objects to roles in transaction SCC4. To do this, enter the switch CLIENT_SET_FOR_ROLES in the table PRGN_CUST and set its value to YES. If this switch is not maintained or is set to a value other than YES, the SCC4 setting will be ignored, which means the old system behavior is active. Note that the switch CLIENT_SET_FOR_ROLES, like all entries in the table PRGN_CUST, is valid system-wide.”

2.Check Prerequisites

  • Check SLD Configuration:
    1. Go to JAVA NWAàConfigurationàScenariosàConfiguration Wizard àFunctional Unit configuration UIàClick on System Landscape Directory àEnable automatically
    2. This step will take time, you have to specify ABAP user and JAVA admin user name & password and Master password to start the step.
  • You can use external Remote SLD or configure New SLD
  1. Start the URL https://:/sld. Choose Administration -> Settings -> Server Configuration, choose the Perform Role Mapping button and confirm.
  • Check post installation on ABAP

Open transaction STC01 and enter task list SAP_BASIS_SETUP_INITIAL_CONFIG.

  1. ◦Create/Select Workbench Request (SE09)
  2. ◦Upload System Profiles (RZ10)
  • ◦Create and assign Logical System to local Client (BD54/SCC4)
  1. ◦Schedule Standard Jobs (SM36)
  2. ◦Create SAP DB connection (DBCO)
  3. ◦Configuration for SLD Data Supplier (RZ70)

Execute and check the log.

  • Initialize or Update SU24 Authorizations

Start transactionàInitially fill the customer tables

Click “Selection includes sap standard applications and then execute.

  • Check Web Service Configuration
    1. Start transaction SOAMANAGER.
    2. On the Service Administration tab, choose Simplified Web Service Configuration.
  • Choose the API Settings tab.
  1. Select the fields Basic Authentication, X.509 Certificate Authentication, and Ticket Authentication.
  2. Save your entries.
  3. Exit the transaction.

Create HTTPS service in SMICM and check SPAU if any correction is there or not and then run automatic activities.

3.Setup connections to SAP

  • RFC connectivity

Fill the required details along with router string and backend suser details from saposs rfc.

  • Setup Hub Connectivity

Configure SOAP Runtime

  1. Start Transaction SBGRFCCONF and select the Define Supervisor Dest. tab.
  2. If an entry is already there, go to the next step. If no supervisor destination exists, press the “Create” button; provide a destination name (default bgRFC), a user name and password then save your entries
  • Start transaction or SRT_ADMIN.
  1. Choose Perform Check on Technical Settingsand then execute.
  2. Choose Check specific clientand enter the SAP Solution Manager local client. Do not change the other settings.
  3. Execute the check.

This will give you the overall status.Task watcher is no mandatory.

To activate required ICF nodes:

  1. Start transaction SRT_ADMIN.
  2. Choose Manual Setup and select the Make Settings
  • Execute

To configure the IDP service:

  1. Start transaction WSIDPADMIN.
  2. Use the default values and choose Schedule.

To create and register the inbound destination in client 000:

  1. Log on to client 000.
  2. Start transaction SRT_ADMIN.
  • Choose Automatic Setup and select the Perform Technical Setup radio button.
  1. Remark: This will create 2 users in client 000: DELAY_LOGON (service) and SAP_WSRT (system)

Create User for Support Hub Communication

 

Please follow this sap note to create SUSER for communication 2174416 – Creation and activation of users for the Support Hub Communication

Specify the configuration parameter:

Once user created and activated, specify the same here.

Computer Name of Access URL: URL to Service Point at SAP

◦Example without SAP Router : servicepoint.sap.com

◦Example with SAP Router : /H//S/3299/H/servicepoint.sap.com

  1. Port Number of Access URL: 443
  2. URL Protocol Information: HTTPS
  • Name of Proxy Host: name of your customer proxy
  1. Port Number of Proxy Host: your customer port number of your customer proxy
  2. User Name for Proxy Access: your customer proxy user name
  3. Password of Proxy User: your customer proxy user
  • Technical User: user created with manual activity : Create User for Support Hub Communication
  • Technical User Password: password of above specified user
  1. SSL Client Store Password: password (if set) to access SSL Client Store in Trust Manager (transaction STRUST)

And then configure STRUST

  1. Create SSL Client SSL Client Anonymo certificate.
  2. Open webpage https://apps.support.sap.com and download the certificate and import into SSL Client Anonymo

Configure Synchronous Communication Channel

Follow the sap note 2289984 to create RFC

  1. Follow SAP note: 2289984 – Configure the synchronous communication channel
  2. Troubleshooting information can be found in 2359837 – “Set Up Connections to SAP” and “Support Hub Connectivity” in Solution Manager 7.2

And then perform the automatic activities.

4.Apply Recent correction.

Correction for SNOTE

Correction for ABAP

Essential JAVA correction

5.Maintain Technical user.

Create all the require users and then complete the system preparation step.

Now we are moving to Infrastructure preparation.

*************************************************************************************

Key point: Infrastructure preparation.

1.Setup Landscape Management

  • SLD Connection:

Create new connection. Define at least one connection with SLD role source for LMDB

  • LMDB Synchronization
    1. Please do not use the Host Name of Solution Manager as LMDB Object Server Name.
    2. Instead use ‘_LMDB’ as LMDB object server name.
  • LMDB Content check

Check & Save.

2.Setup Java Connectivity

  • Define HTTP Connectivity

Provide ABAP application server & Java Application server name with port number and test the connectivity.

  • Enable connectivity

Execute all the automatic steps.

  • Diagnostic Agent Authorization

Generate Agent authentication root certificate and save.

3.Setup BW

  • Confirm SAP BW

Am using 001 solman client as a BW.

CheckàUse SAP BW in separate system or separate solution manager client.

ProvideàABAP Client & user name and password

  • Maintain user

Create all users.

  • Enable SAP BW

Execute all the automatic activities.

4.Define CA Introscope

2285189 – Introscope 10.1 Release Notes for changes and open issues

797147 – Introscope Installation for SAP Customers

Use this sap note to install the CA Introscope and then define the installation path.

ClickàDiscover Introscope EM and provide installation path

Example: E:\usr\sap\ccms\apmintoscope

5.Setup E-mail communication:

  1. Kindly provide SMTP[Node,Host IP,Port,Domain] details.
  2. Execute the RSCONN05 report and activate the required SAPconnect secure E-mail session.
  • Since SAP_BASIS 7.31 SP2, an integrated encryption solution is available. See SAP Note 1637415.
  1. For more information about secure e-mail encryption, see SAP Note 149926.

6.Configure CRM Basics

  • Technically upgrade using start transactionàProgramàCOM_PRODUCT_UPGRADE
  • Deactivate the BdocsàStart transactionàNew entries

SAP Solution Manager creates BDOc messages for the following BDoc types:

  1. BUPA_MAIN
  2. BUS_TRANS_MSG
  3. CRM_IBASE_MESS
  4. PRODUCT_INDOBJ
  5. PRODUCT_SRV

For more information, see SAP Note 635697

And then execute the manual activities.

7.Enable gateway services

Activate the following services:

  1. AGS_FLP_INTEROP
  2. AGS_FLP_PAGE_BUILDER_PERS
  • 1.From the Navigation column, start transaction /N/IWFND/MAINT_SERVICE.
  1. 2.Select one of the above-mentioned services.
  2. 3.In the ICF Nodes section, choose the ODATA entry.
  3. 4.Choose ICF Node and then choose Activate.

And then complete. So we have completed the infrastructure preparation. We will go for Basic configuration.

*************************************************************************************

Key point: Basic Configuration

1.Configure basic function

Execute all the automatic activities.

2.Schedule jobs:

Select allàschedule all the jobs as planned.

3.Configure manually.

  • Business Partner for Scenario Users
  1. To schedule the periodic background job, proceed as follows:
  2. 1.Start transaction BP_GEN.
  • 2.On the entry screen, make the following entries (for all other selection fields keep the default values):
  1. ◦Under RFC Destination, enter NONE.
  2. ◦Under Identify Users and Business partners by, select E-Mail Address if an e-mail address has been defined for the SAP Solution Manager users in transaction SU01.
  3. Otherwise, select User Name.
  • ◦Under Program, uncheck the Test Mode option.
  • 3.Choose Program -> Execute in Background and schedule the job periodically.
  1. 4.Change the user of the background job.
  2. The background job is scheduled for your logged in user. It is strongly recommended to change the user for the scheduled job to the SOLMAN_BTC user which has been defined under SAP Solution Manager Configuration > System Preparation > Maintain Technical Users.
  3. You can do this in transaction SM37.
  • Configuration for Rapid Content Delivery

Follow the sap note to configure this Rapid content delivery to download the content update from marketplace automatically. SAP note : 2383652

Otherwise you can download manually and upload to complete the content update.

  • Delete Session Documents and Download

Start transaction to schedule the jobs to delete the sap session, EWA session and downloads,SLR etc.

  • Service Content Update Configuration

Schedule a job for both content update & Application log cleanup

4.Create basic dialog users

Create all users and complete the basic configuration.

*************************************************************************************

Regards,

Sabarish vasudevan

 

 

Advertisements

TMS RFC communications error with system/destination

Issue:

We have successfully included into the domain controller. But unfortunately we are not able to import the transports because the Current system host is unknown.

Error log:

RFC communications error with system/destination %%ashost=XYZ,sysnr=,lang=E,client=000,pcs=2,
Message no. XT101

Diagnosis
An RFC error occurred in the TMS communications layer.

Target system: XYZ.DOMAIN_ZYX(000)
Function: TMS_TP_MAINTAIN_BUFFER
RFC message: RFC destination %%ashost=VARTGTADB,sysnr=,lang=E,c

System Response
The function terminates.

Procedure
Correct the error and execute the command again.

Solution:

We have found one SAP note and resolved it with option 2. PFB for your quick reference.

1888279 – RFC communications error with system/destination

Please let me know if any further clarification.

Regards,

Sabarish Vasudevan

SAP Remote Basis Administration – Task List

SAP Remote Basis Administration – Task List

Recommended daily tasks
1. Check whether the systems are up
2. Check whether the backups finished without errors
3. Check for alerts in CCMS monitors
4. Check for hanging or stopped work processes
5. Check system log for errors/warnings
6. Check whether any background jobs got canceled for any reason
7. Check the lock entry list
8. Look for any failed updates
9. Check for users logins from unknown terminals/locked users
10. Analyze program dumps
11. Check for excessive swaps and buffer statistics
12. Review Database performance
13. Check database for space critical objects
14. Check the average response times
15. Check for OS level alerts
16. Check CPU load and memory usage
17. Review SAPDBA calendar job logs
18. Check archive directory status

Recommended weekly tasks
1. Check database for free space
2. Monitor tablespace growth
3. Monitor total DB growth
4. Clean up Spool
5. Clean up transport buffers
6. Run TemSe consistency check
7. Review security audit log
8. Check for adequate file system space
9. Analyze Early Watch reports

Recommended monthly tasks
1. Cycle the R/3 system to defragment memory
2. Analyze the database growth and plan for storage
3. Review directory structure and need to move data files
4. Cleanup old logs

Recommended quarterly tasks
1. User security overview
2. Review SAP profile parameters
3. Review the standard scheduled jobs
4. Test the backup by restoring
5. Archive the old transport files
6. Maintain SAPDBA and database parameter files
7. Review maintenance contracts for all hardware / software
8. Check for usage versus licensing

Recommended annual tasks
1. Audit user security
2. Audit profiles and authorizations
3. Review user roles
4. Maintain activity groups/profiles
5. Cleanup clients in test/development systems
6. Check workbench organizer settings
7. Refresh test system8. Simulate disaster recovery/failover testing
Software maintenance (as needed) 1. Applying support packages
2. Applying database patches
3. Upgrading kernel
4. Change Management /applying notes
Additional services (as needed) 1. User Maintenance / Profiles creation and maintenance
2. Printer definition maintenance
3. Data archiving
4. Technical Upgrades
5. Server Migration