cancel
Showing results for 
Search instead for 
Did you mean: 

Domain/local Installation

JAMpe
Participant
0 Kudos

Hello,

I'm about to install some systems in windows server platform so I've some doubts about doing a local or domain installation. According to the installation guides:

You use domain for:

- Distributed systems - Not my case.

- Common SAP Transport - Not my case.

- You want to use SSO (does this mean, for example, when connecting a EP with a backend system?)

You use local for:

- Single machine installation (My case)

My question is regarding connecting SAP systems, for example: SAP ERP with SAP NW (BI) or SAP Portal with SAP ERP, etc; In this cases, Do they all have to be local/domain installations? or I can mix them? for example SAP Portal (local installation) connected to SAP ERP backend (in domain installation).

If I use a local installation and I need web access for Portal or a web dynpro abap, How can I get a FQDN for this systems?

Regards,

JAM

Accepted Solutions (1)

Accepted Solutions (1)

Reagan
Advisor
Advisor
0 Kudos

My question is regarding connecting SAP systems, for example: SAP ERP with SAP NW (BI) or SAP Portal with SAP ERP, etc; In this cases, Do they all have to be local/domain installations? or I can mix them? for example SAP Portal (local installation) connected to SAP ERP backend (in domain installation).

It doesn't matter whether the installations are local or domain for establishing a connection between a BI, EP and / or ECC.

These connections are established using RFC's, JCo RFC. The users used for configuring these connections are stored in the underlying database.

As long as these systems are reachable and can communicate then it is absolutely fine.

Regards

RB

Former Member
0 Kudos

Hi.

First question that i will ask you is what would be the FQDN.

Like Same domain.

ECC.abcd.com

PORTAL.abcd.com

In this case if you have SSO beteen these two system that it will work.

Different domain.

ECC.abcd.com

Portal.local.com

In this SSO will not work till you do domain relaxation using the below parameter.

1368384 - SAP Logon Tickets configuration for non-trusted JAVA systems

701205 - Single Sign-On using SAP Logon Tickets

  • ume.logon.security.relax_domain.level


The host entry solution is just a workaround for testing.

This a very bad solution to deploy for all users in production.

The good solutions have already been given : domain relaxing if possible or reverse proxy in the same domain.

Thanks

Rishi Abrol

JAMpe
Participant
0 Kudos

Thank you both. A few more questions..

- what about SSO? In a local installation will I be able to use SSO, for example, between EP and ERP?

- for using FQDN in a local installation, If my servername is, for example, "srvsandbox", I have to enter in the host file an alias like: "IP srvsandbox srvsandbox.testdomain.com"? Does this "testdomain.com" have to exist? or It can be just an alias?

Regards,

JAM

Reagan
Advisor
Advisor
0 Kudos

- what about SSO? In a local installation will I be able to use SSO, for example, between EP and ERP?

Here is what the installation guide says.

Domain Installation

In a domain installation, the user account information is stored centrally in one database on the domain controller and is accessible to all hosts in the system.

You have to perform a domain installation if one of the following applies:

You install a high-availability system with Microsoft Failover Clustering.

You want to use Single Sign-On with Microsoft Kerberos SSP

You use a common transport host for several SAP systems running on different computers.

According to the installation guide the domain installation is required for SSO based on Kerberos which is basically mapping the Windows users to the SAP users. Read this link:

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/content.htm

For SSO between ECC and EP this shouldn't be a problem.

- for using FQDN in a local installation, If my servername is, for example, "srvsandbox", I have to enter in the host file an alias like: "IP srvsandbox srvsandbox.testdomain.com"? Does this "testdomain.com" have to exist? or It can be just an alias?

I believe this can be just an extension to the hostname.

Regards

RB

Answers (2)

Answers (2)

ahmed_ibrahim2
Active Participant
0 Kudos

Hi JA

only you have to choose either Local installation  or Domain According to your future plane and your company strategy

for Example

if you plane to implement SSO so you have  to choose Domain Installation

but in your case

single machine and Central Instance so Domain installation is not required .

------------------------------

for the second question

IT IS  OKAY you can mix the system installation between Local and Domain whenever the systems can PING each other , but it is not recommended you have to think about unified systems

------------------------------

If I use a local installation and I need web access for Portal or a web dynpro abap, How can I get a FQDN for this systems?

Actually you have to configured the FQDN During your Installation or even after installation 

during Installation

SAPINST will ask you to Enter FQDN

for Example Enter  COMP.net

but you have to define the primary DNS suffix for your computer first

RC on your computer Icon ==>Properties

click Change Settings

click Change --> more

click OK -->OK -->OK

Restart Your System

Best Regards

AhMeD

define the primary DNS suffix for your computer
Sriram2009
Active Contributor
0 Kudos

Hi

You can installation either local or domain(Domain is recommended ), you can add the enter in the local host file on you all the SAP system. so that you can get the FQDN.

In a Domain installation, the user account information is stored centrally in one database on the domain controller and is accessible to all hosts in the system in LAN.

Perform a domain installation if one of the following applies:

-> You install a distributed system (to avoid authorization problems).

-> You install a high-availability system with MSCS.

-> You want to use Single Sign-On.

-> You use a common transport host for several SAP systems running on different computers.

-> You want to setup Disk to Disk Backup Strategy

In a Local installation, all the user account information is stored locally on one host and is not visible to any other hosts in the system. If the SAP system is to run on a single machine (central system), you can perform a local installation.

Regards

Sriram