Centralise System Landscape Directory

[Former Member]

First off, I'd like to say Happy new year everyone..... especially those that assisted me in 2005!

We are having problems transporting through CMS due to having three SLDs - XI3.0 sp12, oracle 9.2.0.6 and windows 2003 cluster.

I have tried exporting the SLD from Dev and importing into QA and Prod, but I get errors.

I think the last option (and probably easiest option) is to centralise the SLD for Dev, QA and Prod.

I assume I will need to set the sldapicust in each client, change the Data Supplier Bridge, exchange Profile and probably some settings in the j2ee administrator.

Is there a document/OSS note that can show me the steps to take?

Can anyone help me bring this matter to a speedy conclusion??

[Former Member]

Barry, a quick one...to use CMS, we need to install JDI. For JDI we need to install NetWeaver Developer Studio which is only supported on Windows 2000 and XP per the documentation. We have Windows 2003 server...now the question: we like to use CMS on Windows 2003...has anyone done it? Any issues? etc. Thanks!

[Former Member]

I have setup CMS on windows 2003.

We do not use the JDI, though. We develop through Websphere and IBM's development studio tools.

We implemented the CMS without using the JDI, having just a Dev, consoldiated and Productive landscape.

[deidre_logan]

I am having a simular problem trying to move our Central SLD from our XI development server to our XI production server.

I followed the Note 720717

When I do the system checks

test SM59 connection SAPSLDAPI - ok

transaction SLDCHECK - get an error under the LCR_LIST_BUSINESS_SYSTEMS but I debugged and found it is having a issue with the function SLDJAVA_ACCESSOR_REQUEST with RC 21 which is Communication failure.

test SXMB_IFR - OK

create a new software componenet in new SLD and see it in SXI_CACHE and be able to import it into the Integration Repository.

Cache Connectivity test in the Component monitor - OK

I think the error is in how the RFC destinations are setup with the Java Jco RFC registered programs. I would like to verify when I am suppose to use the XI integration server host or the Central SLD host.

There are 2 RFC destination in SM59 that are used by the SLD from what I can see LCRSAPRFC and SAPSLDAPI.

So if I am on my XI development system on XI_DEV and my new SLD is on XI_PRD. So when creating the JCO RFC destination I log on to my XI_DEV unix server. I start the visual admin. I dgo to the "JCO RFC Provider" service. I click on the SAPSLDAPI connection. Under RFC destinations the Gateway Host and Gateway Server are still the XI_DEV information? And under Repository I have the application host and system number and client of the XI_DEV system? correct?

The only thing I should be changing in the visual admin to the new SLD server on XI_PRD is the "SLD data supplier" service under the HTTP tab to point to the new SLD on XI_PRD?

Why does note 720717 say to change the SM59 connection of SAPSLDAPI to the gateway on the new SLD which would by in my case XI_PRD? with the registered program with the new SLD... I did try this and we had test messages showing up in the production system.... very bad. Why does the note not refer to LCRSAPRFC.

I did not think this was going to be a difficult task but I am getting very frustrated. So I want to understand which parts of the config are running on the XI Integration Server and which parts of the config should be on the new SLD server.... I have many documents and one says use the Integration Server host and another saying to use the New SLD host.

Thanks for your assistance.

Dede

[MichalKrawczyk]

Hi Barry,

happy new year:)

>>>Is there a document/OSS note that can show me the steps to take?

sure there are:)

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

<b>question 2</b> - <b>SLD</b> section will help you:)

(oss note + sld document)

Regards,

michal

[Former Member]

You're a gentleman.

Thank you for you speedy response (points awarded).

Regards

Barry Neaves

[MichalKrawczyk]

>>>You're a gentleman.

hehe:) why's that?

>>>Thank you for you speedy response

no problem Barry:))

Regards,

michal

[Former Member]

hahaahhaa...

[Former Member]

Well, it wasn't as straight forward as I thought....

I followed the OSS Note 720717.

Changed sldapicust, sm59, RZ70 and exchangeProfile on QA.

When amending the SLD Data Supplier in Java Admin Console, On test connection, I get the following error:

Operation Failed! Failed to collect SLD data. Software caused connection abort: socket write error.

I have double checked the user names and passwords as per note 721548, but still getting this error.

I rebooted the Java engine but that didn't help....

When logging onto Integration Direcotry and check cache notification, I get the following error:

Unable to determine the name of the central Adapter Engine from the System
Landscape Directory at this time. 
Notifications to the central Adapter Engine are therefore listed using the technical name 
of the Adapter Engine. 
This is usually structured as follows: af.<SAP System ID>.<Name of application server>

I assume I need to amend something else....

Point 6 on the note says If you are using adapter engines, make sure the SLD accessor points to the new SLD, but doesn't explain what to do....

Can anyone help??

Regards

[MichalKrawczyk]

hi,

did you do all those tests:

Please perfrom the following tests:

1) Test the connection SAPSLDAPI in transaction SM59

2) Call transaction SLDCHECK and check if the correct SLD is accessed

3) Call transaction SXMB_IFR and click on the link to the SLD. Does it connect to the new SLD?

4) Create a new Software Component Version in the new SLD and try to import it into the respective Integration Repositories.

Regards,

michal

[Former Member]

Michal

I think I have highlighted the problem, but identifying the solution may be harder....

The Problem is the user XILDUSER keeps getting locked.

I have changed the password on QA (abap) and amended in connection in the exchangeProfile and j2ee - SLD data supplier.

Every thirty seconds or so the user gets locked and I can'twork out why....

Can anyone help??

Regards

[Former Member]

Hi Barry,

When I went through the forum for ur problem I found that user may get locked If you have mentioned wrong passwords for the same user at Different places(QA,Prod).

Check this thread

Here the AFUSER is locked due to incorrect password at QA system.

Hope this gives some reference to your problem.

Cheers,

Rashmi

[Former Member]

Thanks for your response Rashmi.

I was following note 721548 and have synchronised the passwords in all clients in all systems, amended the SLD connection parameters, changed the SLD Data supplier in Java Admin Console, changed the exchangeProfile, but only Dev and Prod have their passwords locked every few minutes....

Is the XILDUSER used anywhere else in config, on either Java or ABAP??

[Former Member]

A message relative to this topic, I am just trying to connect an XI system to a central SLD and I am getting the following error.

Calling function EXCHANGE_PROFILE_GET_PARAMETER

Retrieving data from the XI Profile...

Function call returned exception code 3

Access to the XI Profile is currently disrupted.

=> Check whether you can access the XI Profile using a web browser!

Could anyone see the problem here???

Thanks

Thilothama

[Former Member]

I was getting this message when the xilduser was locked.

[Former Member]

I have now resolved this issue by rebooting the Java Engines.

[Former Member]

I am using XIAPPLUSER - I can use any user right? also checked in SU01 and the user is not locked.

Rebooted the java engine and still didnt work

Thanks for the replies.