Connectivity & Destinations

When an AS Java application needs an outbound connection to an EIS, what are the two ways that connection can be opened?

The destination service manages connections to an EIS. Which connection types can it administer, and which type is typical for an AS ABAP target versus an AS Java target?

For an HTTP-type destination that points at an AS ABAP, how is the target addressed, and what extra data can you store beyond the endpoint?

When an administrator creates a new JCA Connection Factory (giving it a JNDI name), what else is created automatically, and which object actually carries the communication?

A destination's Logon Data offers several authentication mechanisms. Which does SAP suggest you prefer over plain user/password, and what is the full set of options?

What does an RFC-type destination specify, and at what point can it operate without a gateway?

An RFC destination needs a gateway. On which instances does a usable gateway live for an AS ABAP target versus an AS Java target?

For instance number 10 of a target system, what gateway service and port would an RFC destination use, and how is that value derived?

For inbound RFC into an AS Java, which side initiates the call, which AS Java service receives it, and what must already be in place beforehand?

To let an AS ABAP send RFC into an AS Java's JCo RFC Provider, what must be created on the ABAP side and how does it reference the Provider?

In the JCo RFC Provider server configuration, Server Count is set to 5. How does the Local JCo Servers option change the total number of connections opened to the gateway?

Under the Java Connector Architecture, how many resource adapters does an AS Java need in order to communicate with a given type of EIS?