Common transport directory configuration

Dear Gurus,
I installed ECC6.0 sr3 (dev and quality on the same server) windows 2003. Production server on seperate server. Now I want to configure common transport directory.
For dev and qas using same transport directory beacuse they are in the same server.
But production server is having seperate transport directory.
Is it compulsory having the common tranport directory.
Can Any body give the steps to add the production server in the same tranport directory.
Regards
Rao.

Is it compulsory having the common tranport directory.
No, it is not compulsory.
You can use STMS tcode to configure the same.
For further information, please go through the below link:
[Transport Management System|http://help.sap.com/saphelp_erp60_sp/helpdata/EN/44/b4a0137acc11d1899e0000e829fbbd/frameset.htm]
Regards,
Faisal

Similar Messages

Common Transport Directory

Hi Experts,
I have some doubt about the procedure to setup a common transport directory.
Lets assume I have a 3 systems landscape (Windows env) with DEV,QTY and PRD systems. After installing SAP on the three servers, now I have to include the above systems in a common transport domain. I want DEV system to be my domain controller.
My doubts are:
1) Before configuring DEV as domain controller using STMS, do I need to share /usr/sap/trans dir for this system ?
2) (Assume /usr/sap/trans dir for DEV is shared by now) After I include the QTY and PRD system into this domain using STMS, How will the QTY and PRD system understant that they shud use the shared "/usr/sap/trans " dir of DEV and not their local /usr/sap/trans. Do I manually edit some settings for QTY and PRD systems to achieve this ? Please let me know exact steps that are involved.
Thanks !
Mandeep

Hello,
Try the following.
http://www.sap-img.com/basis/how-to-do-the-tms-configuration.htm
And also,
STMS configuration.
1.Login to 000 client with user DDIC
2. goto STMS --> prompts to create a domain controller --> check with entries and save.
3. goto systemoverview -->SAP system --> create virtual system ( For QAS and PRD)
4.goto Transport routes -->change --> configuration --> standard configuration --> three system in group --> enter SID's --> specify Three system configuration and distribute configuration to all systems.
Once you created virtual systems and then goto transport routes and configutation -->change --> standard configuration --> threesystem group. specify SID's of three systems and save then specift three system configuration and distridute configuration.
Once you have done above thing add QAS and PRD in to landscape.
1. Login to PRD system 000 client with DDIC user.
2.STMS --> prompts to create domain controller > select other configuration and add to existing domain controller ( i.e DEV because DEV is domain controller).> specify system details for PRD system.
3.Once you added and saved. login to DEV system --> 000 with DDIC --> stms --> system overview --> select PRD system --> SAP system --> Approve and save.
4. follow the same steps for QAS also.
5. A communication user will be created between domain controller and remaining systems in a landscape. ie TMSADM
6. the entire configuration will be stored in DOMAIN.cfg file in trans/bin folder
I hope this information will helpful to you.
Note: Points always encourage me to reply !!

Need common transport directory(heterogeneous)

Hello All,
I have to include three ECC 5.0 systems and three BW systems into Domain controller( Production solman 7.0)
1) Three ECC 5.0 System are running on Red Hat Linux (OS)
2) Three BW systems are running on Red Hat Linux (OS).
3) Domain Controller (solman) is running Windows 2003 server
Above situation is Heterogeneous environment.
Now i have to configure common transport directory for all above systems ( seven systems), which are running on Different OS like Red Hat Linux and Windows 2003 Server.
For common transport directory what are the steps have to be done...?
Please help me out.
Thanks and Regards,
Kiranbabu

Kiran-
What i think is you need to work with CTS+ configuration and please see the OSS note: 1003674 this is the central note which might be handy for you.
http://help.sap.com/saphelp_nw70/helpdata/en/45/ec25370fdc3481e10000000a1553f6/frameset.htm
Hope this might help you some way

Common Transport Directory Migration

Our ERP 6.0 system is running on Windows 2003 Server 64 bit. The default install created a separate transport directory on each CI host. As a result users do not have log information of their transports into the PROD system, from the DEV or QAS systems. Currently they have to log into each instance to get their transport log information from the transport organizer.
I have read the online help and reviewed the SAP Notes on creating a common directory however I have not found any solid information to assist migrating/merging an already existing TMS setup. .
I have created the following check list in preparation to merge the separate transport directories into a common transport directory. Is there anything I missed?
1. Schedule maintenance to ensure Business analysts/Developers are out of all ERP systems.
2. Backup the entire \usr\sap\trans directories on DEV, QAS and PROD before beginning.
3. Update the TMS Domain Profiles for each respected system with the common directory path of the Transport Domain Controller. In our case it is the Dev server.
DIR_TRANS = \\hostname\sapmnt\trans
4. Merge the following QAS directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
5.Repeat with the PROD directories into the respected DEV directories (Confirm to overwrite existing files)
\usr\sap\trans\cofiles
\usr\sap\trans\data
\usr\sap\trans\logs
Te goal is to insure that the delta changes between PROD, QAs & DEV are fully merged.
Common Transport directory
[http://help.sap.com/saphelp_erp60_sp/helpdata/EN/de/6b0da5f34d11d3a6510000e835363f/frameset.htm]
Thanks,
Jon Sells

We tried to implement this migration of the common transport directories and it was not successful. We ended up restoring back to the individual EPS directories.
What happened is that the QAS Queues did not reflect all the correct transports. (Yes, Siddhesh, I did as you said) In addition the add to buffer (crooked arrow) not longer functioned for newly released transports from DEV.
Does anyone have a white paper or SAP Note that would help on Migrating a common Tranpsort directory for Windows? Our Developers & Analyst do not like having to logon to each system to see view the transport logs. They are under the impression that they shoul be able to use SE10 in DEV and see the transport/import logs.
Thank you
Jon Sells

How to share Common transport directory with Production

Dear All,
we are following three-system landscape with Dev & Qas on the same server & production server in a Cluster.Now I am going to start the production server installation but I have few query before starting the installation:
1. The Dev+Qas server is sharing a common transport directory (/usr/sap/trans). The production server needs to share the same transport directory.I have few options:
a)Should I need to share the common transport directory during the installation
b)I install the production server first then I can share the transport directory which is currently being shared by Dev & Qas system
c)I need to share the Common transport directory first & then start the installation so that during installation Production system writes into the Common traansport directory
Please advise.
Thanks in advance,
Sandipan

Hi,
By mounting, do you mean just to share it as we are using Windows Server 2003 x64 bit system, so just by sharing will it work.
Need your suggestion on whether can I install the production system first & then by sharing the transport directory from Dev( or Qas) it can join in the exisitng transport directory. As during installation of production server also,the system will create /usr/sap/trans. If I don't share the already exisitng /usr/sap/trans of Dev system, can I share it later so that production system can join into the common transport directory without any problem.
Please guide,
Thansk & Regards,
Sandipan

How to set CTD ( common transport directory ) ????

i need it pls help me ........?????

Hi,
Please reade below link and implement accordingly.
http://help.sap.com/saphelp_nw70/helpdata/en/de/6b0da5f34d11d3a6510000e835363f/content.htm
http://help.sap.com/saphelp_sm32/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Regards,
Anil

I want to change the transport directory

Hello gurus,
I want to change the tranport directory in all our systems. Please advise me how to do it.
I really appreciate your help.
Regards,
N.S

Hi N.S,
How about :
http://help.sap.com/saphelp_47x200/helpdata/en/d5/10b4496f0f11d2b41a006094b9ea64/frameset.htm
is it common transport directory ?
To change the common transport directory configuration, you can
first go to transaction AL11 of one of your system, for example, PRD.
Change the 'DIR_TRANS' parameter, so that it points to the directory that you want to change
Then go to STMS, choose 'System Overview' button to display systems
of your transport domain. Double click PRD, with 'Transport
Tool' tab, click 'Display <-> Change' button, you can change the
'transdir' value.
Please make sure it is equal to the same configuration of 'DIR_TRANS'.
Repeat the above steps on your other system. Make sure the configurations
of 'transdir' and 'DIR_TRANS' are the same as that on the PRD system.
cheers,
Vincent

Change the Transport Directory.

Hi everybody, We have I system installed (S01) and we have just installed a new one (S02), we want to be able to trasnport from the system S01 to the system S02. What I have to do in order to do that?
I read that the systems have to have the same Transport Directory. And I checked with AL11 and the values for the DIR_TRANS parameter are the following for each system:
system S01 -> DIR_TRAN ->
S01\sapmnt\trans
system S02 -> DIR_TRAN ->
S02\sapmnt\trans
I tried to change the DIR_TRANS parameter with the transaction RZ10, but in S02 we don't have any profile.
Cuold you please help me to do that?
Thanks and Regards.

Hi,
read that the systems have to have the same Transport Directory.
not neccesary to have tarnsport directory, it depends upon scenario.
Pls follow the below link for configuring stms configuration.
bbs.cenet.org.cn/UploadImages/200581112435749207.pdf
Also check the below link
Common tranport directory on Windows local installation
Thanks,
Anil

Change STMS transport directory

Hi gurus,
I have a High Availability SAP ERP system (SAP ECC 6.0) as PRD server. We used an old server for DEV system (Host name = sapdev). These two servers belonged to a STMS domain.
Recently we made homogeneous system copy and created a new Development (PRD copy) system to a new server. the new servers host name is AthinaDEV. We created a new STMS domain, joining the new DEV and PRD systems. The problem is that transport directory in PRD seams to be
sapdev\sapmnt\trans\ and in DEV seams to be
athinadev\sapmnt\trans\. In both servers in Transport Tool I have configured TRANSDIR as
athinadev\sapmnt\trans.
How can I change the transport directory to PRD to look
athinadev?
Thanks in advanced

OK,
I added the profile parameter DIR_TRANS with the correct path to both systems and now both systems use
athinadev\sapmnt\trans as transport domain. All seems to be correct now (all checks return success) but I can't transfer any request.
For example: I have created a test ABAP program. I have created a request for that program. I released the request from SE11 transaction succesffully. But when I use STMS transaction I have the following situation: in import overview I can see both systmes and 1 request waiting. When I double click on PRD to enter to import queue the list is empty.
I have cheked the permissions on trans folder and seems to be ok (prdadm has corrrect permissions).
The two systems has connected with transport routes.
Can anyone help me find the solution?

The TMS configuration is inconsistent and The transport route configuration

Hi,
I logged on domain controller in STMS in QA. I can see the following in STMS as
" The TMS configuration is inconsistent
The transport route configuration is inconsistent"
Users were able to do transports and there were no issues.
Transport routes
DEV>QA>PRD
TST(which is not active)
Environment:
Oracle: 10.2.0.4.0
Windows NT
Netweaver 70 ehp1 abap
Please guide me how to resolve the above issue.
Thanks and Regards
Satya

Hi,
Everything is tick marked.
Please find the output.
Check Transport Directory                                 03/30/2011 08:34:16
       QA1 CAL - Quality
           Transport Directory
               bin
sap2bksrv\sapmnt\trans\bin
               Create Test File
               Read Test File
               Delete Test File
          buffer
sap2bksrv\sapmnt\trans\buffer
                Create Test File
                Read Test File
                Delete Test File
          cofiles
sap2bksrv\sapmnt\trans\cofiles
               Create Test File
               Read Test File
               Delete Test File
         data
sap2bksrv\sapmnt\trans\data
              Create Test File
              Read Test File
              Delete Test File
         log
sap2bksrv\sapmnt\trans\log
             Create Test File
             Read Test File
             Delete Test File
         sapnames
sap2bksrv\sapmnt\trans\sapnames
             Create Test File
             Read Test File
             Delete Test File
         tmp
sap2bksrv\sapmnt\trans\tmp
             Create Test File
             Read Test File
             Delete Test File
Thanks and Regards
Satya

Same transport domain. different transport directory, possible?

Hi SAP folks,
A quick query, I work on multiple systems within a single SAP transport domain. Recently we have requirements to move 2 non-ABAP systems to a different transport directory while keeping the rest intact.
The reason for this is we are doing CTS+ for the 2 non-ABAP system and do not want to share the transport directories for the rest of the ABAP system.
Please advise if this can be done and how?
The following link for SAP suggested that it's possible but stop short of how to do it.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/6045377b52253de10000009b38f889/content.htm
Anyone done similar setup? care to share?
Thank you.
Regards,
Jansen

Hi,
You can do this very well. First you should remove the two systems that you wanted to configure for CTS+ from your existing transport domain. To do this, login to your existing transport domain controller and delete the systems you wanted to remove from transport domain.
To perform this:
STMS --> Overview -> Systems -> < choose the system u want to delete> -> SAP Systems -> Delete. Confirm the deletion and save and activate the changes made to ur configuration.
And then add your Non-ABAP systems you wanted to configure for CTS+ using the domain controller you decided for CTS+.
I hope this help you to perform your action.
Best Regards,
Vasanth Govindaraj

Unable to use global transport directory

Hi,
I have a 3 system SAP landscape consisting of DEV, QAS, PRD. I configured TMS and put all three system into the same transport group. DEV and QAS can shared the same transport directory residing in DEV. However I am unable to get PRD to use the global transport directory. PRD is always using its transport directory. How can I allow PRD to use the global transport directory?
Rdgs

Hi,
The transport directory is shared out which explains why QAS is able to use the same transport directory. DIR_TRANS in PRD points to local transport directory and not the shared transport directory. Is there really a need to set DIR_TRANS parameter if TMS is configured? In QAS, I don't see DIR_TRANS being set in the instance profile.
I did tried setting DIR_TRANS in PRD however the system reported the parameter as unknown.
BTW, PRD is a copied from another system. We migrated the old PRD to a new server.
Rdgs

Error checking transport group configuration in System BQS

Hi Everyone,
I made a client export from Production to Quality. It went successfully,, I noted the requests numbers and transported them from PRD to Quality, but while transporting there was a tp error(which i did not note), next i went to the quality import queue and saw all the 3 requests had come. But when i click the adjust queue icon im getting the following error message "Error checking transport group configuration in System BQS" . Afterwards i tried to delete the requests from quality to retransport from production but still im not able to delete those requests from quality. Can anyone help me solve this.
Regards,
Rahul

Hello Rahul,
regarding the error message:
"Error checking transport group configuration in system"
It's mostly related to the TMSADM RFC destination. Kindly follow the below mention steps:
1. Logon to client 000 with user DDIC.
2. STMS > System > Overview > Select the system in which you are logged in > Click on the menu says EXTRAS > Generate RFC Destinations
Perform the above steps in all the systems configure in your TMS. This should resolve the issue.
Best regards,
Tomas Black

Integration Directory(Configuration) Problem

Hi All,
I am facing one Probelm. I am working one the client through Citrix. I am not able to open Integration Directory(Configuration Problem) . In onsite it's working fine. Reming all other applications(Integartion Repository and SLD and Runtime work bench) are working fine.
if I open Integration Directory i am getting this messge.
<jnlp spec="1.0+" codebase="http://filp55.group.upm-kymmene.com:50100/dir">
    <information>
        <title>Integration Builder</title>
        <vendor>SAP AG</vendor>
        <homepage href="http://www.sap.com" />
        <description type="one-line">Directory</description>
        <description type="short">Directory</description>
        <description type="tooltip">Directory</description>
        <icon hight="64" href="start/graphics/sap6464.gif" type="splash" width="64" />
        <icon hight="32" href="start/graphics/SAP3232.gif" width="32" />
    </information>
    <security>
        <all-permissions />
    </security>
    <resources>
        <j2se version="1.4+" initial-heap-size="32m" max-heap-size="1024m" />
        <jar href="directory/aii_ibdir_client.jar" />
        <jar href="directory/aii_ibdir_core.jar" />
        <jar href="directory/aii_ibdir_sbeans.jar" />
        <jar href="directory/aii_ibdir_rb.jar" />
        <jar href="directory/aii_ib_client.jar" />
        <jar href="directory/aii_ib_core.jar" />
        <jar href="directory/aii_ib_sbeans.jar" />
        <jar href="directory/aii_ib_rb.jar" />
        <jar href="directory/aii_util_icons.jar" />
        <jar href="directory/aii_util_swing.jar" />
        <jar href="directory/aii_util_xml.jar" />
        <jar href="directory/aii_util_xsd.jar" />
        <jar href="directory/aii_utilxi_misc.jar" />
        <jar href="directory/aii_util_rb.jar" />
        <jar href="directory/clientaii_ib_sbeans.jar" />
        <jar href="directory/clientaii_ibdir_sbeans.jar" />
        <jar href="directory/frog.jar" />
        <jar href="directory/focus14.jar" />
        <jar href="directory/sapxmltoolkit.jar" />
        <jar href="directory/jta.jar" />
        <jar href="directory/ejb20.jar" />
        <jar href="directory/exception.jar" />
        <jar href="directory/logging.jar" />
        <jar href="directory/guidgenerator.jar" />
        <jar href="directory/jperflib.jar" />
        <jar href="directory/sapni.jar" />
        <jar href="directory/sapj2eeclient.jar" />
        <property name="sap.theme" value="Streamline" />
        <property name="jnlp.log.initialConfiguration" value="FILE, SIMPLE" />
    <property name="jnlp.com.sap.aii.ib.client.properties" value="com.sap.aii.ib.client., com.sap.aii.ib.core., com.sap.aii.util.xml., com.sap.aii.connect., com.sap.aii.repository.mapping.additionaltypes, com.sap.aii.docu., com.sap.aii.ibrep.core., com.sap.aii.ibdir.core.*" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.connect.landscape.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.cr.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.ib.client.content.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.repository.contextroot" value="rep" /><property name="jnlp.com.sap.aii.ib.client.login.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.directory.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.cr.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.rwb.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.directory.contextroot" value="dir" /><property name="jnlp.com.sap.aii.connect.rwb.contextroot" value="rwb" /><property name="jnlp.com.sap.aii.connect.landscape.httpsport" value="@com.sap.aii.server.httpsport.lcr@" /><property name="jnlp.com.sap.aii.connect.repository.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.repository.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.cr.httpsport" value="@com.sap.aii.server.httpsport.cr@" /><property name="jnlp.com.sap.aii.connect.repository.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.contextroot" value="run" /><property name="jnlp.com.sap.aii.connect.integrationserver.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.rwb.httpsport" value="@com.sap.aii.connect.rwb.httpsport@" /><property name="jnlp.com.sap.aii.connect.landscape.httpport" value="50000" /><property name="jnlp.com.sap.aii.docu.languages" value="null" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.initialheapsize" value="32m" /><property name="jnlp.com.sap.aii.util.xml.parserFactory" value="com.sap.engine.lib.jaxp.SAXParserFactoryImpl" /><property name="jnlp.com.sap.aii.connect.directory.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.httpsport" value="@com.sap.aii.server.httpsport.directory@" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpport" value="8001" /><property name="jnlp.com.sap.aii.connect.rwb.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.cr.httpport" value="50000" /><property name="jnlp.com.sap.aii.connect.landscape.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.SAPMYNAME" value="filp55_GTX_01" /><property name="jnlp.com.sap.aii.connect.rwb.httpport" value="50100" /><property name="jnlp.com.sap.aii.docu.url" value="null" /><property name="jnlp.com.sap.aii.ib.client.applicationname.directory" value="sap.com/com.sap.xi.directory/" /><property name="jnlp.com.sap.aii.util.xml.transformerFactory" value="com.sap.engine.lib.jaxp.TransformerFactoryImpl" /><property name="jnlp.com.sap.aii.ib.client.applicationname.repository" value="sap.com/com.sap.xi.repository/" /><property name="jnlp.com.sap.aii.ib.client.login.InitialContextFactory" value="com.sap.engine.services.jndi.InitialContextFactoryImpl" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpport" value="50100" /><property name="jnlp.client" value="true" /><property name="jnlp.com.sap.aii.connect.repository.httpsport" value="@com.sap.aii.server.httpsport.repository@" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.maxheapsize" value="1024m" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpsport" value="@com.sap.aii.connect.integrationserver.httpsport@" /><property name="jnlp.com.sap.aii.connect.integrationbuilder.startpage.url" value="rep/start/index.jsp" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpsport" value="@com.sap.aii.connect.integrationserver.r3.httpsport@" /><property name="jnlp.com.sap.aii.connect.rwb.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.util.xml.schemaValidator" value="com.sap.engine.lib.schema.validator.SchemaValidator" /><property name="jnlp.rc.release" value="7_00" /><property name="jnlp.rc.applname" value="DIRECTORY" /><property name="jnlp.rc.supportpackage" value="09" /><property name="jnlp.rc.synctime" value="${sync.time}" /></resources>
    <application-desc main-class="com.sap.aii.ibdir.gui.appl.ApplicationImpl">
        <argument>webstart</argument>
    </application-desc>
</jnlp>
Please help me on this..........
Thanks in Advacne.
Regards,
Chandra

Hello,
1)
May be the problem is a network connectivity issue. Do one thing copy the "cahce" folder from some other client PC(which has successfully opened IR and ID) to your client PC. The folder resides in "C:Documents and Settings<yourUserProfile>Application DataSunJavaDeploymentjavaws".
Copy "cache" folder to your client PC under the above path.
/people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]
2) Go to http://filp55.group.upm-kymmene.com:50100/rep/
Click on Administration -> Java Web Start -> Java Web Start Administration ->
Try
1. Re-initialization (then try logging)
2. Re-initialization and force-signing (then try logging)
3. Delete lock (then try logging)
Do this for IR and ID tabs.
3) Check can be a firewall issue.
4) Check wether sufficient roles have been assigned -> Tcode -> SU01 -> roles tab. These roles need to be assigned to your username
SAP_BC_AI_LANDSCAPE_DB_RFC
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_XI_BPE_CONFIGURATOR_ABAP
SAP_XI_BPE_MONITOR_ABAP
SAP_XI_DEVELOPER
SAP_XI_DEVELOPER_ABAP
SAP_XI_DEVELOPER_J2EE
SAP_XI_MONITOR
SAP_XI_MONITOR_ABAP
SAP_XI_MONITOR_J2EE
<b>*******************Reward,if found useful</b>
Edited by: BVS on May 7, 2008 3:01 PM

MS active Directory Configuration on SAP 4.7 and ECC6.0

Hello
Can anybody guide the steps required for MS Active Directory Configuration with SAP 4.7 on AIX and
and ECC 6.0 also on AIX 5.3.
Currently we are using many different applications on client landscape.
The requirement is for implementing the Single Sign On for all the applications
on the client landscape.

Please check
/people/andre.fischer/blog/2008/06/04/windows-server-2008--active-directory-certified-for-the-bc-ldap-usr-directory-interface-for-user-management
In Case you also have EP then
/people/wai-hon.lam/blog/2006/04/20/windows-integrated-authentication-via-kerberos-on-an-ldap-data-source
Also check below for SSO
Note 121178 - NT: Installation note for SSO Single Sign On
Note 138498 - Single Sign-On Solutions

Common transport directory configuration

Similar Messages

Maybe you are looking for