cancel
Showing results for 
Search instead for 
Did you mean: 

Generate Remote Connection for our Solution Manager 7.1

wmarcy
Contributor
0 Kudos

Hi,

In order to complete installation of SAP Solution Manager 7.1, we need to send a message to SAP Support through SOLMAN but we still don't have a RFC connected to the SAP backbone.

Anyone get a process easy-to-understand and to set up, we're in France and it's very urgent.

Currently we've set up correctly installation of back-end and front-end, we can logon to solution manager and it's all.

If you have ever done an installation of Solution Manager with Remote Connection, please join me.

Best regards,

William

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

After installing the Solution Manager 7.1 system did you run the solman_setup transaction for the required configuration?

This wizard will guide you through all the steps. Creating a remote connection to SAP using an S-USer is covered as a part of this wizard run. Suggest you to check the WIKI page for solution manager setup run:

http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home -> 7.1 -> System Preparation and Basic Configuration links.

Regards,

Srikishan

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi All,

I got solman_setup run-time error after upgrade the solution manager 7.1 SP04 to SP08.

Aafter applied this1741470 snote its working.

Thanks,

Srinivas T.

wmarcy
Contributor
0 Kudos

Thanks for advices.

Remote connection works well and we sent our GoLive throught the support portal.

Regards,

wmarcy
Contributor
0 Kudos

Hello

First thanks for the help.

We decided to perform a local ( not domain ) installation for a central system.

SOLMAN-SRV is the Hostname of the server

The computer wasn't on the domain i added it with an admin account ( now it's on the ca-c.adds domain ).

I managed to access SAP Solution Manager Configuration ( Solman_setup) via a tweek of the web address : http://solman-srv.ca-c.adds:8000xxxxxxxxxx

Now i can access the setup but i have an error message asking to be logged as a Solman Administrator with the possibility to create/edit users.

I think i have two main steps :

1st : manage to access solman_setup webpage without tweeking the adress

2nd : configure the users / profiles / roles but i looked everywhere and i can't manage to find the documentation about the profile setup : How to copy an account, which rights to set, which users create , ...

I wonder if it wasn't a mistake not to perform a domain installation, i checked on the installation guide and if i want to change to a domain installation its advised to check the documentation System Copy for SAP Netweaver : is it really necessary ? we are supposed to access the web interface with a local installation as well : it maybe an error during the installation or due to a lack of configuration during the post-installation ?

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi William,

Local or domain, is not relevent to FQDN. That is reuqired in any solman configuration.

You don't want to tweak the web address (URL). You want to define the fully qualified domain name in

the Instance profile with parameter icm/host_name_full.

During Installation you would have create an <SID>ADM user.

It sound sto me like you have skipped over some post-installation steps, and gone straight to Solman_setup.

You will have numerous problems if you do not complete the installation ( post-installation steps), before

begining Intiial (preliminary and basic configuration - solman_setup).

Please review the installation manual, and review the post installation steps and ensure you cover everything off before trying to run Solman_setup.

Regards,

Pauk

wmarcy
Contributor
0 Kudos

Hi.

Thanks for the suggestion.

Unfortunatly we already attempted to use the SOLMAN_SETUP transaction but we had some errors :

[logon screen|http://imageshack.us/photo/my-images/846/logone.png/]

[Error|http://imageshack.us/photo/my-images/851/erroraew.png/]

We are using the SAP* user , on the 001 client.

Any help would be much appreciated.

Former Member
0 Kudos

Hi,

The errors are due to missing prerequisite settings before the solman_setup run.

First, I recommend to set the profile paramter values as below:

login/create_sso2_ticket=2

login/accept_sso2_ticket=1

Second maintain the ICM host profile parameter value:

icm/host_name_full = <saphost>.sap.com

ICM hostname parameter should be a FQDN (fully qualified domain name).

Maintain the above via RZ10 tcode and a restart of system is required for these to take affect.

Also, run the solman_setup as an administrative user (copy of ddic or sap*).

Would recommend you to go through the configuration guides and http://service.sap.com/rkt-solman -> Solution Manager 7.1.

Here check the settings required before starting solman_setup. There are few more profile parameter settings required.

Regards,

Srikishan

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello,

Did you download and follow the Installation Guide?

http://solman_srv:8000

Is NOT a Fully Qualified Domain Name (FDQN)

A Fully qualified name would have the format

Host.Company.Domain

i.e. http://service.sap.com is fully qualified, while http://service is not.

This is the first problem you are having, but I suspect you have more, as at this point in the installation SAP* should already been disabled and your Admin user accounts setup. This would have been durng the post installation steps, which are performed prior to Solman_setup.

Yes, you need to defined parameter icm/host_name_full to equate with the FQDN of solman-srv.

Second thing is that client 000 and client 001 are reference clients provided by SAP. You don't want to be changing these clients. You want to be copying these reference clients to your clients and then configuring those clients, not your reference clients, as this will cause a problem when you need to create new clients.

Did you follow the installation guide carefully? I would recommend you review, because it covers off these things, so you shouldn't be running into these errors at this point in the configuration phase, if you followed the Installation guide (especially the POST Installation steps)

Regards,

Paul