How to configure product system and technical system to run Maintenance Optimizer
Friday, 26 August 2011
Maintenance Optimizer Notes
Note 1344564 - Maintenance Optimizer: Check system landscape
How to configure product system and technical system to run Maintenance Optimizer
How to configure product system and technical system to run Maintenance Optimizer
Wednesday, 24 August 2011
Register SAP Java system in Solution Manager (SLD)
The following steps detail how to register an SAP Java system (version 7.1 or higher) in Solution Manager (SLD) without using Visual Administrator
Log into NetWeaver Administrator http://<host>:<port>/nwa
Navigate to Configuration Management -> Security -> Destinations
Create 2 (*) new destinations which point to the Solution Manager system:
SLD_Client - user ID supplied must have SAP_SLD_DATA_SUPPLIER role or better
SLD_DataSupplier - user ID supplied must have SAP_SLD_GUEST role or better
Click Home to return to previous NWA screen
Navigate to Configuration Management -> Infrastructure -> SLD Data Supplier Configuration
Click on Collect and Send Data
System data will now be in the Solution Manager's SLD. Check in http://<solman host>:<solman port>/sld and navigate to Technical Systems -> Web AS Java
To ensure it's also in SMSY run 'Landscape fetch' background job.
Info from here:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90f7d52e-8637-2e10-5caf-950dd1a4a42c?QuickLink=index&overridelayout=true
(*) Following page suggests only the SLD_DataSupplier destination is required:
http://help.sap.com/saphelp_nw73/helpdata/en/48/b6847d96655295e10000000a42189b/content.htm
Log into NetWeaver Administrator http://<host>:<port>/nwa
Navigate to Configuration Management -> Security -> Destinations
Create 2 (*) new destinations which point to the Solution Manager system:
SLD_Client - user ID supplied must have SAP_SLD_DATA_SUPPLIER role or better
SLD_DataSupplier - user ID supplied must have SAP_SLD_GUEST role or better
Click Home to return to previous NWA screen
Navigate to Configuration Management -> Infrastructure -> SLD Data Supplier Configuration
Click on Collect and Send Data
System data will now be in the Solution Manager's SLD. Check in http://<solman host>:<solman port>/sld and navigate to Technical Systems -> Web AS Java
To ensure it's also in SMSY run 'Landscape fetch' background job.
Info from here:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/90f7d52e-8637-2e10-5caf-950dd1a4a42c?QuickLink=index&overridelayout=true
(*) Following page suggests only the SLD_DataSupplier destination is required:
http://help.sap.com/saphelp_nw73/helpdata/en/48/b6847d96655295e10000000a42189b/content.htm
Monday, 8 August 2011
Trusted System Set-Up
Ensure an RFC connection from the remote system to the trusted system (and vice versa) exists
Ensure the RFC connection does not have 'Trusted System' option ticket
Run transaction SMT1 in remote system
Click Create
Enter the name of the RFC connection to the central system
Enter log in details
Save new entry
Run SMT1 in the central system to create connection to the remote system and repeat steps above
Run SM59
Change RFC connection so that the 'Trusted System' option is selected
Ensure the RFC connection does not have 'Trusted System' option ticket
Run transaction SMT1 in remote system
Click Create
Enter the name of the RFC connection to the central system
Enter log in details
Save new entry
Run SMT1 in the central system to create connection to the remote system and repeat steps above
Run SM59
Change RFC connection so that the 'Trusted System' option is selected
Wednesday, 3 August 2011
Thursday, 12 May 2011
SAP SRM Catalogues HTTP HTTPS Switch
If access to the Portal is secured with HTTPS, opening catalogues can result in web page errors.
The inbound and outbound handlers needs to be bypassed in order to make the switch successful:
Run SPRO
Go to Supplier Relationship Management -> SRM Server -> Master Data -> Content Management -> Define External Web Services
Select the catalogue
Double click Standard Call Structure
Add the following:
Parameter = BYPASS_OUTB_HANDLER, Value = X, Type = Fixed value
Parameter = BYPASS_INB_HANDLER, Value = X, Type = Fixed value
Click Save
The inbound and outbound handlers needs to be bypassed in order to make the switch successful:
Run SPRO
Go to Supplier Relationship Management -> SRM Server -> Master Data -> Content Management -> Define External Web Services
Select the catalogue
Double click Standard Call Structure
Add the following:
Parameter = BYPASS_OUTB_HANDLER, Value = X, Type = Fixed value
Parameter = BYPASS_INB_HANDLER, Value = X, Type = Fixed value
Click Save
Updating and Repairing SLD
For updating the SLD refer to SAP note:
Note 669669 - Updating the SAP Component Repository in the SLD
For repairing the SLD refer to SAP note:
Note 1093168 - Repair of SLD CR content
Build the reference SLD using an import of data from the same model version and CR data version as the afflicted local productive SLD.
Run the CRRepair process to rebuild the sld/active SLD to a clean version of the data.
Note 669669 - Updating the SAP Component Repository in the SLD
For repairing the SLD refer to SAP note:
Note 1093168 - Repair of SLD CR content
Build the reference SLD using an import of data from the same model version and CR data version as the afflicted local productive SLD.
Run the CRRepair process to rebuild the sld/active SLD to a clean version of the data.
Tuesday, 1 March 2011
Testing connectivity to monitoring agent
saphostctrl.exe -host hostname -function GetComputerSystem
If this fails the port is probably closed.
If this fails the port is probably closed.
Subscribe to:
Posts (Atom)