Creating JCo Destinations 

Use

If you choose Create JCo destination in the Web Dynpro Content Administrator, a wizard opens with which you can define a new JCo destination.

You can find details about the SAP Java Connector in the SAP Library under SAP NetWeaver ®  Application Platform (SAP Web Application Server) ® Connectivity ® Components of SAP Communications Technology ® Communications Between ABAP and Non-ABAP Technologies ® SAP Java Connector.

If you are using an adaptive RFC model in a Web Dynpro application, you must define two JCo destinations:

·        The application gets metadata from the first connection.

·        The application gets the application data from the second destination.

Prerequisites

You have administrator rights for the J2EE Engine.

Procedure

...

       1.      Define general data
Define a logical name for the JCo destination. This name must be unique and you should choose a self-explanatory name. At runtime the JCo connection is implemented with a JCo pool. You must define the largest possible pool size. This is the maximum number of connections that can be set up at runtime. You also define the client.

       2.      Define the J2EE cluster
Assign the JCo destination to a J2EE Engine cluster. A cluster is a distributed system of the J2EE Engine dispatcher and other server elements that appear to the client as a unit.
The default is the locally installed J2EE Engine and it is labeled Use local J2EE Engine.

       3.      Define the data type and connection type

In this step you select the data type for the JCo destination. You can choose one of the following values in the radio button group

¡        Dictionary metadata

¡        Application data

You then define the destination type. It can be one of the following:

¡        Load-balanced connection

¡        Single server connection

The destination type for data type Dictionary metadata can only be a load-balanced connection. You therefore cannot select a single server connection.

There are two destination types available for data type Application data.

However, you should only use a single server connection for debugging a Web Dynpro application.

 

       4.      Define the application server or message server
Below you can define the application or message server type, depending on the selected connection type. If you are using a SAProuter, you can also define the SAProuter string in this step. If you selected connection type Load-balanced connection, you must define a message server.
For more information about the SAProuter, see the SAP Library under SAP NetWeaver ® Security ® SAPNetWeaver Security Guide ® Network Infrastructure ® Firewalls ® SAProuter.

       5.      Define the security settings
You have to take security matters into consideration and define the security settings when you specify a JCo destination.
You first select the required authentication method for user authentication.

¡        If you select „User/Password“, you must define a user and the corresponding password.

¡        If you select „Ticket“, ticket authentication is expected and you need not define a user and password.

¡        The same is true for „Client Certificate (X509)“. You need not define a user and password here either.

You also have to make the settings for Secure Network Communication (SNC).

Note that you have to make other settings to activate the Secure Network Connection on your J2EE Engine. For detailed documentation about security, see the SAP Library at SAP NetWeaver ® Security. For information about SNC, see SAP NetWeaver ® Security ® SAPNetWeaver Security Guide ® Network Infrastructure ® Transport Layer Security ® Secure Network Communications.

       6.      Summary of the defined parameters
The last step of the wizard gives you an overview of the defined parameters. To change parameters, navigate back to the location to be changed with Previous and make the corresponding changes.
You end the wizard with Finish. You have now created a new JCo destination.

You can also edit the JCo destinations you created by selecting Maintain JCo destinations in the toolbar of the Web Dynpro Content Administrator.