Adapters Running in the Adapter Engine (Java
SE)
This section summarizes how you can secure adapters running in the Adapter Engine (Java SE).

The Adapter Engine (Java SE) is only supported for
compatibility reasons. It hosts only a subset of the adapter functionality and
has fewer security features. You should only use this Adapter Engine if it is
a precondition in your environment. More information:
Working with the
Adapter Engine (Java SE).
The
Plain J2SE Adapter Engine (Java SE) has a separate user and password
management, which is not integrated into the overall SAP NetWeaver user
administration. More information:
Configuration.
It provides three user roles for interactive users:
● Adapter Engine administrator
With this role, you administer the Adapter Engine. It includes the user administration itself.
● Adapter configurator
With this role, you configure the individual adapters.
● Adapter user
With this role, you can view the adapter configurations.
Additionally, there is a role for messaging, which has to be assigned to users that send messages to this Adapter Engine:
● HTTP server user
With
respect to password management, you should always store passwords in the
tokenized and obfuscated form as documented in
Password
Management.
You should enable SSL for all HTTP-based communication to and from the Adapter Engine (Java SE):
● Communication to and from the Integration Server
● Communication to and from an external SOAP communication partner
If possible, you should also encrypt the communication to and from the JMS provider.
The
Adapter Engine (Java SE) uses SSL for both communication line encryption and
client and server authentication using certificates. A certificate store is
available. More information:
Certificate
Management.
All configuration data for the Adapter Engine (Java SE) is maintained in flat property files.
The file for the engine administration data itself is located in the following directory:
<installation directory>/tech_adapter/BaseConfiguration
The file for the adapter configuration data is located in the following directory:
<installation directory>/tech_adapter/Configuration

The adapters of this Adapter Engine are configured locally and not in the Integration Directory. Exchanged messages are also stored directly in the file system.
Therefore, ensure that only the operating system user, who has started and therefore owns the adapter engine process, can read the property files and has access to the directories used for message exchange.