on 2005 Nov 28 4:51 PM
Why should I register my j2ee engines in SLD when configuring JDI?
I have done this and able to see my systems in SLD. but when will JDI use this system information.
Thank you
Hi Reddy,
when creating tracks in CMS the information where to find the development configurations is transmitted to the SLD.
I´m not totally sure but it would make sense if the SLD uses the system information of your J2EE engine for telling the developer (better the NWDS) at which host, port, ... to find the development configuration.
Regards
Helmut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
AFAIK, the dev config is stored in SLD and imported into NWDS from SLD.
but my doubt is all the j2ee engines of dev, tst and prod should be registered in SLD. why?
we do this in visual admin -> cluster -> server -> services -> sld data supplier -> runtime -> http settings. This is repeated for dev, tst and prod.
Thank you
Hi Reddy,
the dev. config is stored in the CMS database. The SLD only knows where to find these.
You do not have to register your runtime J2EE engines in SLD but you should and there should be one SLD for the whole company. Regarding the last point there are also other solution possible but it is recommended just to have one SLD.
You have to register your J2EE engines if you work with Web Dynpro and the adaptive RFC Model. You cannot define JCO destinations if you haven´t registered in SLD.
Regards
Helmut
You only need to do it for the WebAS that hosts JDI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.