Jco Connections

[Murali_Shanmu]

Hi

Why do we always create Jco in Pairs. One for Model Data and one for Meta Data. Can anyone give an elobrate view on this.

Regards,

Murali`

[Former Member · Accepted solution]

Hi,

If you use an adaptive RFC model in a Web Dynpro application, two JCo destinations are automatically created in the Web Dynpro Content Administrator.

·With the first connection, the Web Dynpro application receives the metadata that is not user-specific and that is therefore the same for all users. It must be available to all users : WD_RFC_METADATA_DEST.

·With the second connection, the Web Dynpro application receives the application data, which is normally user-specific : WD_MODELDATA_DEST.

Regards,

Satyajit.

Message was edited by: Satyajit Chakraborty

[Former Member]

Hi,

A connection to get the needed (dictionary) meta data information

A connection to get the read the application data

So that the Model and Meta data

Use the Thread--http://help.sap.com/saphelp_nw2004s/helpdata/en/f8/bdfe80d9a3b048a5fb32a7d149774e/frameset.htm

Regards

Saravanan K

[Former Member]

HI,

Creating the JCO connections

The logical system names used in the model declaration must be associated with an actual SAP system defined in the SLD before this application can be executed. For this reason you need to create JCO connections in the Web Dynpro Content Administrator. To use an adaptive RFC model in your Web Dynpro application you will define two connections:

<b>A connection to get the needed (dictionary) meta data information</b>

<b>A connection to get the read the application data</b>

Detailed description is given here

<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/f8/bdfe80d9a3b048a5fb32a7d149774e/frameset.htm">JCO</a>