Solman_setup - Landscap Data

Dear All,
I am configuring Solution Manager EHP1 using solman_Setup.
Which infomation entered during Wily Introscope Enterprise Managers in Lnadcap Data -> Basic Configuratin.
Regards,
Nirav

Hi Nirav,
Please go through the below link for downloading Wily Introscope
If it is already installed in your server.. you can find in services as Introscope* if it is in Windows
Downloads->My Company's Application Components" SAP SOLUTION MANAGER" SAP SOLUTION MANAGER 7.0 EHP 1" WILY INTROSCOPE ENTPR MGR" WILY INTROSCOPE ENTPR MGR 8.. download for your relevent OS.
Please go thru Wily Documentation for detailed installtion and set up
Regards,
Laxman

Similar Messages

Automatic forwarding of landscape data

Hello
We have a DEV and CONS system, each with its own SLD. The XI content trasport is intended using CMS. Also, the two SLD's need to be synchronized via automatic forwarding of landscape data.
Where can I find a suitable document giving the complete procedure for SLD synchronization ?
Thanks,
- Shankar

Hi Shankar,
As far as i know there aare no docs available which describe this process in detail.
Also you will have to use the import and export method to export the SLD objects for the first time. In my opinion Automatic forwarding of SLD data is only for the changes that have been to these objects once they have been imported for the first time. However i am not very sure about this. You may try refering to the Config Guide for XI and the How To CMS guide.
Regards
Sidharth
Sidharth

Downloading landscape data from SMSY

Hello All,
Does anyone know how to download landscape data from SMSY ?
Is there a transaction/menu path which allows you to download the landscape data into a spreadsheet or something ?
Regards,
Siddhesh

Try this:
http://www.sappro.com/downloads/UsingSLD.pdf
Thanks
Kalyan
Pls reward if answer is helpful

Best way to manage different landscapes data in solman

Hello,
We are interested in using certain solman functionnalities to our complete customers landscapes.
Our situation is that we manage the SAP landscape of many diferent customers. Each landscape is maintained individually from the others. We would like to enter the data of those landscapes into our solman.
But this causes some issues with duplicate SIDs for instance. Indeed several landscapes share the same SID for different systems. A direct consequence of this is that the wizard used to create system RFCs will have trouble with duplicate users, since it uses the SID to create the users on the solman (SOLMAN<SID>).
A way to workaround would be to define those users manually, but maybe that solman has a functionnality to handle these situations ?
Thanks in advance for sharing your thoughs.
aidan

Hello,
If you have customer A landscape with SID's XXX, YYY, and XYZ under Installation 12345678 and customer B landscape with SID's XXX, YYY and XYZ under installation 23456789. Solution Manager will have no problem distinguishing Customer A systems from customer Bs systems, even though they have the same SID. It is not the SID that needs to be unique, it is the installation Number + the SID that needs to be unique.
And Customer A would never have systems installed on Customer B's installations. Thus I do not see there is an issue here.
However If customer A has a duplicate SID under the SAME installation number, this can cause a number of problems, especially anything related to service sessions. In fact in regards to EWA's SAP Note 1257308 - FAQ: Using EarlyWatch Alert
mentions this in the section 5. Restrictions and Prerequisites, second point...
Identical SID and installation number:
EarlyWatch Alerts are identified by the key <Installation Number>
and <SID>. It is not possible to process EarlyWatch Alerts for
two SAP NetWeaver based systems with the same SID and
installation number in one Solution Manager.
But you could utilize a second Solution Manager to accomplish this if required.
The Note also describes how to deal with Stand By systems, where they would have the same name, for instance in a fail-over scenario or a disaster recovery situation.
You do realize that you can utilize clients to group users, so you can create a client for each of your customers, because the RFCs created by the wizard follow the format SM_<SID>CLNT<Client>_* (BACK, TMW, TRUSTED, READ, ETC). So the client will be unique to each customer.
So I hope this helps.
Regards,
Paul

System Landscape Directory for Portal 7.0

Good Day All,
Currently we are running Portal 7.0...now we are planning to run TREX 7.0 on our landscape.
In the post instlation guide of TREX its mentioned that we need to register the TREX on the System Landscape Directory (SLD).
Can we uitlize the SLD running on EP 7.0 JAVA AS or we should have a stand alone JAVA AS for SLD separately.

Hi Demorgan.
The purpose of SLD is gathering and updating landscape data automatically. In other words you do not need to gather this information manually, e.g. - in Excel sheets.
Thus from the functional point of view it doesn't matter either TREX is registered in SLD or not. It's about how you maintain your system landscape.
Best regards,
Aliaksandr Zhukau
P.S.: You can find information resources about SLD here [System Landscape Directory (SLD)]

Adding existing systems to a new Solution Manager 7.0 Ehp1 system

Dear Experts,
We've just installed a new Solution Manager 7.0 Ehp1 system, we have a 3 system landscape in action, please need your help to connect these systems with this new Solution Manager system. The post installation Initial Configuration and Basic Configuration has been performed successfully. Also need your help with Maintenance Optimizer configuration and setting up EWA.
Please do share experiences, links and documents for the above.
Thanks in advance,
Best Regards,
basis-novice

Page 65-67 of Netweaver EHP2 Upgrade Guide found in service.sap.com/instguides.
You can use the explanation below to configure MOPZ and maintain systems in SMSY.
4.5.2Configuration of the Maintenance Optimizer
You have to configure the Maintenance Optimizer. For a list of configuration tasks, see the Maintenance Optimizer Configuration Guide.
Make sure that you run the guided procedure SOLMAN_SETUP after every installation or update of SAP Solution Manager and that it completes successfully.
Related Documents
Available at...Maintenance Optimizer Configuration Guide http://service.sap.com /mopz (link at the bottom of the page)
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.5.3Maintaining System Landscape Information
The Maintenance Optimizer relies upon up-to-date information about your system landscape. Therefore you have to maintain this data in SAP Solution Manageru2019s system landscape (transaction SMSY). In the following, you will find the description how to maintain this data. If you already have maintained the system landscape data, then check if the data is correct.
If you use the System Landscape Directory (SLD), then use it to capture the system data.
If you do not use the System Landscape Directory (for example, if you have a pure ABAP system), you use RFC connections to maintain the data.
Procedure
Maintaining the System Landscape Data Using SLD
1.
Register both Java systems and ABAP systems that you want to update in your central SLD.
The central SLD can either be on your SAP Solution Manager system, or you can have a separate system where you run the SLD (central runtime SLD). If you use a central runtime SLD, make sure that it is synchronized with the local SLD of your SAP Solution Manager system.
4.
Create an RFC connection
1.
Choose the Client tab for your system.
2.
Maintain at least client 000.
3.
Create an RFC connection between the Solution Manager and the system you want to update using the RFC Assistant.
5.
Start the data transfer
To initiate the remote transfer of system data from the target system, choose the Read System Data Remote.
RECOMMENDATION
We recommend you to schedule automatic data transfers using transaction SMSY_SETUP.

Is Wily Introscope a requirement with Solman 7 ehp1

We are finishing and upgrade from 3.2 to 7 EHP1.
Due to limited system capacity we have not installed the Wily Introscope product. At this time we were not planning on using its functionality. We are wanting to keep the basic functionality of solman 3.2 plus add the MOPZ piece.
I'm using the solman_setup tcode to go through the basic config wizard now. I've reached the Landscape Data step where it is asking for the Wily Introscope info. Since it doen't exist, can I bypass this step?
Thanks for your advice.
Laurie McGinley

Thanks Jarad,
That is what I thought (it isn't required), but needed to double check before I bypassed that bit of the setup.
Appreciate the quick response too!
Laurie

SolMan vs Wily

Hi,
The SolMan was installed while ago.
Now we want to configure the Wily for J2EE systems monitoring.
I have installed the "Introscope Enterprice Manager 8" using the the guide available at marketplace. I have also deplyed the agent's SCA file on SolMan.
It did not ask me anything about the SolMan. I am wandering how the SolMan will know about it.
The only thing I found it that go to SOLMAN_SETUP and choose "Landscape Data" under Basic configuration for Wily Manager.
Then choose "Manual Configuration" to import the "Wily Introscope Agent". Once this is successfull then I am good to push the agent to managed system.
Am I in the right direction?
Please let me know if I am missing anything.
Regards,
SC

Hello,
Everything you need to know to configure Wily Introscope in Solman is located in the media library at
http://service.sap.com/diagnostics.
You really should be reviewing this documentation before you started, however it should guide you to complete the installation properly.
Regards,
Paul

Suggestions - predictive text and text entry

I don't know if this forum is intended for suggestions but here are a couple anyway.
1. Because email and sms text do not operate in landscape mode the keyboard is very small. This leads to a large number of text entry errors compared to ther devices I have used. The screen sensitivity is excellent so this is ont a problem with using a touch device. Allowing landscape data entry would go a long wawy to solving this problem - the keyboard when used with safari in landscape mode is a lot better (perhaps 10% of the missed keys). An alternative which would be better for single handed use would be to ditch the qwerty layout and have a key pad that runs to 4 or 5 rows of keys instead of 3. In most cases it is only neccesary to see a single line of text entry so there is plenty of screen re-estate to do this.
2. The predictive text feature on the iPhone is very poor. This is due to a fundamental error in its design. The current implementation assumes that the current word typed is complete but may be misspelled. To be more useful the feature needs to assume that the characters typed are correct and suggest complete words that start with the fragment available. The predictive text in Windows mobile is infinately better that that of the iPhone (and one of the few features I miss from my old phone!).
If this is the wrong place for posting these suggestion - sorry

This is a user to user forum. To submit feedback to Apple, use this form:
http://www.apple.com/feedback/iphone.html

Prblem Service Desk configuration in Solution Manager 4.0

Hi All,
Here I have done the configuration of Service Desk in Solution Manager 4.0 by using the document which I have for release 3.2. However I have face some problem in Step Initially create and Assign the Satellite Systems as iBase C and Manually create and Assign the Satellite Systems as iBase Co .So I exclude above mention step. But still I am able to create the support message from Satellite Systems.
So can please let me know whether it will work fine in upcoming time or Do I need to test my Service Desk configuration for same.
Moreover please let me know how to test Service Desk configuration for real time environment.
Following are the step and problem which I face while doing the Service desk configuration.
STEP 1 #Initially Create and Assign the Satellite Systems as iBase C
To be able to use the Service Desk and Change Request scenarios in SAP Solution Manager, you need to define the Installed Base (iBase). An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
The iBase components for the iBase structure SOL_MAN_DATA_REP (installation 1) can be created and assigned either automatically or manually. Note that these components and the assignments can only be created once automatically for every solution. To refresh your existing iBase data execute IMG activity Manually Create and Assign the Satellite Systems as iBase Components.
Requirements:-
You have defined your system landscape in the Solution Manager System Landscapes(transaction SMSY).
Activities:-
1. In transaction SOLUTION_MANAGER, open a solution.
2. Choose Operations -> Service Desk.
3. Choose Edit -> Initial Data Transfer for iBase.
The data is copied automatically. The iBase systems for the solution are automatically assigned to SOL_MAN_DATA_REP (installation "1"). An iBase component is created for each system installation number (which can be displayed by choosing System -> Status).
For each solution repeat these steps.
Problem in STEP1 :- I am not able to check the System  Status.
STEP 2 #Manually Create and Assign the Satellite Systems as iBase Co
In this IMG activity, you define the Installed Base (iBase) manually, i.e. for refreshing existing iBases after solutions have been changed.
An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
Activities:-
1. In transaction Change Installed Base (IB52), use the input help (F4) to find the Installed Base with external ID SOL_MAN_DATA_REP.
2. Continue as follows:
 If SOL_MAN_DATA_REP does not exist:
a) Call transaction Create Installed Base (IB51).
b) Choose iBase Category 01 (Installed Base).
c) Choose Enter.
d) Specify the iBase header data in the iBase section.
e) Specify the external ID SOL_MAN_DATA_REP and enter a short description.
 If SOL_MAN_DATA_REP exists:
a) Choose iBase No. 1 (SOL_MAN_DATA_REP).
b) Choose the SAP WEB AS component.
3. To assign the systems as iBase components, go to the Text item tab.
Three components are included in the standard package.
4. Add all the satellite systems as text items to the table:
o Column Short text: Description of the system
o Column Identification: System ID, space, installation number
5. Save.
After changes have been made to a solution, repeat these steps to update system landscape data for iBase.
Note:-
Every system is only listed once in the iBases. That means a system is not listed in an iBase if it has been listed in another iBase before.
Problem in STEP2:- Here I am not able to find Text item tab as per point 3 .
STEP 3 # Assign Business Partners to iBase Components
You need to assign business partners to the new iBase components.
Activities:-
1. In transaction Change iBase (IB52), choose Goto -> Partner
2. Assign business partners with the following functions to the new iBase component systems:
o Administrator
o Key User
o Sold-to Party
3. Save.
4. Repeat these steps for each iBase component.
Problem in step3 :- In IB52 t-code screen there no any menu path like goto  partner
Thanks a lot,
Harshal

Hi Harshall,
You have to enter the value as 1 in Installed base field and then press enter.
You will be taken inside and then you will be able to see the Goto - Partner screen.
Hope this will help.
Please reward points suitably.
Regards,
Naresh.

Solution Manager 4.0 Configuration: SLDAPIUSER role

In SPRO, SAP Reference IMG -> SAP Solution Manager -> Basic Settings -> SAP Solution Manager System -> System Landscape -> Automatic System Landscape Data Capture -> Connection of System Landscape Directory to Solution Manager -> Generate authorization roles for SLD users
When I display user SLDAPIUSER in client 001, there are no roles defined. I cannot continue with Authorizations without this role. Does anyone know what the default role for this user should be?
Regards,
Vince Ingram

Hi Vincent,
After my 1st reply I was goind through "Component Installation Guide: SAP NetWeaver 2004s Java on Windows: MS SQL Server", this what I found want in that document:
In transaction SU01 create the following dialog users (you do not need to assign them to a role):
Caution
You must have changed the initial passwords of these users [page 77] before you start the installation of the Java system.
ADSUSER:
User for Adobe document services
SLD Data supplier user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD data supplier user name that you enter later on during the Java system installation must be identical to this user.
Recommendation
We recommend that you name this user SLDDSUSER
SLD ABAP API user (optional):
You only have to create this user if you want to install SAP System Landscape Directory (SLD). The SLD ABAP API user name that you enter later on during the Java system installation must be identical to this user.
Recommendation
We recommend that you name this user SLDAPIUSER
I dont know I am still confused about these users because they have been used in services.
Thank You,
Indasena Janga

How to Setup Service Desk and CHARM in Solu Man 4.0

Hi Gurus
I am New to Solution Manager 4.0 and i want to setup Service Desk and Change Request Management for my client. Any one help me to guide where i can start and after configuring how the functionality of service desk and change request management.
Can anybody send the documents with screen shot how to configure and how it lokks after Configuration.
My client requirement is he wants to make Service desk as a ticketing tool and Charm as Change management tool
Please help me
Piont rewarded for solution
Rajesh

Hello
I have configured Ibase for Charm, i followed spro config info as follows:
Manually Create and Assign the Component Systems asiBase
In this IMG activity, you define the Installed Base (iBase) manually, that is for refreshing existing iBases after solutions have been changed.
An iBase component has to be created for each satellite system from which Service Desk messages will be sent to the SAP Solution Manager system.
For the Value Added Reseller (VAR), it is not absolutely necessary to manually define the iBase at this point. We recommend, however, that you carry out this step so that you have a functioning test scenario.
Activities
1. In transaction Change Installed Base (IB52), choose iBase No. 1 (SOL_MAN_DATA_REP).
2. Create under the IBase Header (SOL_MAN_DATA_REP) an IBase component, for example the SAP component system (SAP WEB AS) or use an existing one.
3. To assign the systems as iBase components, go to the Text item tab.
Three components are included in the standard package.
4. Add all the satellite systems as text items to the table:
Column Short text: Description of the system
Column Identification: System ID, installation number, client
5. Save.
After changes have been made to a solution, repeat these steps to update system landscape data for iBase.
Note:
Every system is only listed once in the iBases. That means a system is not listed in an iBase if it has been listed in another iBase before.
If the identification is not entered correctly, the system cannot correctly identify the component from the incoming Service Desk message.
Its really good and I have set up the config in that way only.
If useful reward the points.
Thanks
Regards
Sharmishtha

Accessing SLD through web services

is it possible to call the SLD via web services to pull out system element data (i.e. different data types like SAP system, application system, database, so forth)? if not are there other APIs to the SLD (like a Java API or C/C++) which could be used by non-SAP programs to get at SLD landscape data?
thanks ín advance / matthew

Hi,
it is possible to access SLD via WS and also there is some API available but I have not done this myself.
this link might be helpfull:
http://help.sap.com/saphelp_nw70/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/frameset.htm
greetings Georgi

MDM limitations?

I would like to
1) What is the maximum number of fields that can be created in main table?
2) What is the maximum number of fields that can be created in qualified table?

Hi Subin,
1) What is the maximum number of fields that can be created in main table?
There is no such thing as maximum limit of fields on Main Table.
It all depends on the following:
1.Business requirement - The data model heavily depends on Business requirement.
e.g If you want to maintain Material master data the number of fields can be more as compared to Customer master data.
2.Customer requirement - This is also a major driver in deciding number of fields.
e.g If Customer wants to have most of data in MDM he can have a repository loaded with fields whereas if MDM maintains only global data then MDM will be having fewer fields.
3.Landscape - Data Model and number of fields are also influenced by the type and nature of systems talking to MDM.
e.g One might require few remote system specific fields etc.
4.Workarounds and Design - It is up to the designer of the Data Model to optimize the number of fields in the repository.
Many a times one has to put in dummy or extra fields just to achieve some requirement,which normally is not achievable in normal scenario.
5.Future Enhancements - Many customers wish to create extra fields so that there future requirements are met.
This is also business driven.
6.Data Model - It is upto Consultants to optimize this and make a healthy scalable Data Model with optimum number of fields.
Choice of table and data flow governs this.
2) What is the maximum number of fields that can be created in qualified table?
Again here there is no fixed rule on this.But main deciding factor here is the fields in a Qualified table should be logically connected.
Also here one has to consider if for One line item in main table are you getting multiple line items,if yes then one can put this in Qualified table or Tuples.
e.g If field belongs to MARA table it should be in Main table and if it belongs at plant level it should be at Qualified or Tuple level.
As a healthy practice all Lookups should not have more than 30% of data content.
Hope this helps.
Thanks,
Ravi

SLD Datasupplier - Technical System Sychronization

I understand that SLD 7.0 and 7.1 employ "automatic forwarding" that updates all data supplier targets with new system information. But, is there a nightly synchronization job between the master and slave SLDs that synchronizes technical systems between master and slave?
In our scenario, we supplied the wrong SLD user in the slave SLD which we assume is the reason why technical system synchronization from Master to Slave did not occur. Now, we need this information in the slave SLD but are unsure if a synch job will run nightly, daily, weekly, etc.

Hi
In 7.0 you can either use export/import to sync the content - if you use export line "LD" only the technical system data will be exported/imported, but you can also use export line ALL to export/import all SLD content (Content Repository, Landscape data, Namespaces and manuel entered data).
However the "automatic forwarding" will eventually update your target with ALL systems that functions as SLD datasuppliers, but yo have to wait until all data-suppliers has run.
BR
Tom Bo

Solman_setup - Landscap Data

Similar Messages

Maybe you are looking for