|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
ClientPassportManager | The JDSR Passport Manager Interface for client connections to an SAP ABAP application server backend. |
DestinationDataEventListener | The DestinationDataEventListener interface reacts on the events that a DestinationDataProvider could fire if the destination configuration was changed. |
DestinationDataProvider | The JCo framework defines the DestinationDataProvider interface to retrieve the destination configuration that must be implemented by infrastructure components. |
JCoSessionReference | A JCoSessionReference is a simple reference to a session or scope in a runtime environment that implemented and registered a SessionReferenceProvider. |
PasswordChangeHandler | This interface allows the implementation of a handler that prompts the user for a new password, which is then used for This is useful if a UI is available, and the password in the backend for the designated user is supposed to be changed before working with the user. |
ServerDataEventListener | The ServerDataEventListener interface reacts on the events that a ServerDataProvider could fire if the server configuration was changed. |
ServerDataProvider | Applications using the JCoServer functionality, i.e. |
ServerPassportManager | The JDSR Passport Manager Interface for server connections to an SAP application server ABAP backend. |
SessionReferenceProvider | The session reference provider can be implemented by a runtime environment that has a session concept in order to provide JCo a simple reference to a session. |
Class Summary | |
---|---|
DefaultSessionReferenceProvider | DefaultSessionReferenceProvider is a sample implementation of the SessionReferenceProvider supporting client sessions running in separate threads (all operation in a thread belongs to the same client session) and server sessions. |
Environment | The Environment class is the central anchor for embedding JCo into an existing application (server). |
Enum Summary | |
---|---|
DataProviderException.Reason | An enumeration for describing the reason of a DataProviderException . |
SessionException.Type | An enumeration for describing the situation when a SessionException is thrown. |
Exception Summary | |
---|---|
DataProviderException | A DataProviderException can be thrown by a DestinationDataProvider or ServerDataProvider
in order to signal severe issues in an existing configuration or some other internal error, like
a wrong setup. |
SessionException | A SessionException is supposed to be thrown by a SessionReferenceProvider in case of issues within session management for sessions that have been initiated by a JCoServer connection. |
Provides all interfaces that are offered for embedding JCo into an application server. In addition to
that the Environment class contains all necessary methods for dealing with the infrastructure components.
Typically, only infrastructure programmers will have the need to deal with that package. Business
application logic typically can be developed without knowing the infrastructure. Details are available
from the single interface descriptions.
Recommendations:
DestinationDataProvider
. Only if there is no
fitting provider available, you could deploy a seperate archive with
the infrastructure component, for which you have a general implementation that is fitting to your needs.
Or even better, you delegate it to the administrator who can decide for the infrastructure implementation he
likes best. If the default implementation included in JCo is fitting well enough, you even don't have
to deploy anything. Never require to have always your specific implementation installed on an arbitrary
application server.DestinationDataProvider
should not be used in productive
environments, as it stores the password in clear text in the file system (<DEST>.jcoDestination).
It is supposed to be an easy configuration possibility for prototypes and tests.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |