Storing passwords in SAP PI modules.
Setting user and password inside a module is slightly different from normal adapter module parameters as the text can’t be kept in clear-text in module parameters.
Three strategies we can use:
1) Hard coded values: Use hard-coded user id and password in the module. Not a great approach but sometimes this can be the only feasible option. The advantage of course is that there is no risk of locking the user.
2) Comm channel params starting with specific strings: Setting in comm channel as a secure parameter ( displayed as asterisk ).
Here, user can be set as a normal string parameter. For passwords, we don’t want the password to show up in clear text. Hence, password can be the following:
The advantage is that the values can be configured for each system and the drawback being if the password is not correctly entered it can get locked and trying to find the comm channel which is locking the user can be time consuming.
3) Setting values in Application Properties. This combines the best of both worlds – we’re able to configure values in each environment and as we’re configuring it in only one location, the chances of accidentally locking the user due to incorrect values is reduced.
i) for >= 7.1 environment
The values can be modified from NWA. The path is:
Configuration Management->Infrastructure->Java System Properties
Steps required to add configuration capacity.
a) Add sap.com~tc~je~configuration~impl.jar to the module EJB project.
Path to get the client library: /usr/sap/<SID>/<instance>/j2ee/cluster/bin/services/configuration/lib/private/sap.com~tc~je~configuration~impl.jar
b) Create sap.application.global.properties file under META-INF. It’s essentially a .properties file.
Sample content to make User modifiable and appear as clear text
## Comment for user
#? secure = false; onlinemodifiable = true
#% type = STRING;
User =
Sample content to make User modifiable and appear as asterisk when entering in NWA.
## Comment for password
#? secure = true; onlinemodifiable = true
#% type = STRING;
Password =
c) Update module code to read the property
Sample code will look something like this ( to be added in the module code )
// Obtain the JNDI context
InitialContext ctx = new InitialContext();
// access the Application-Configuration-Façade service
ApplicationPropertiesAccess appCfgProps = (ApplicationPropertiesAccess) ctx.lookup("ApplicationConfiguration");
java.util.Properties appProps = appCfgProps.
if (appProps == null) {
// perform error handling
}
else
{
userID = appProps.getProperty("
password = appProps.getProperty("Password");
}
d) Update application deployment descriptor to indicate the library being used. Add this to application-j2ee-engine.xml .
<reference reference-type="hard">
<reference-target provider-name="sap.com"
target-type="service">
tc~je~appconfiguration~api
</reference-target>
</reference>
ii) For 7.0 environment
a) Replace
ApplicationPropertiesAccess appCfgProps; |
appCfgProps = (ApplicationPropertiesAccess) ctx.lookup("ApplicationConfiguration");
java.util.Properties appProps = appCfgProps.getApplicationProperties();
by
ApplicationConfigHandlerFactory cfgHandler = (ApplicationConfigHandlerFactory)ctx.lookup("ApplicationConfiguration");
java.util.Properties appProps = cfgHandler.getApplicationProperties();
b) Update application-j2ee-engine.xml
<reference reference-type="hard">
<reference-target provider-name="sap.com"
target-type="service">
tc~je~appconfiguration~api
</reference-target>
</reference>
c) Update the property in Visual Admin:
Server -> services -> configuration adapter-> Runtime -> Display configuration-> Configurations -> apps -> <YOURAPP>-> appcfg -> Propertysheet application.global.properties
d) it can be displayed in.
Analysis->Configuration
Local System->apps-> sap.com-> <YOUR APP >-> appcfg -> Propertysheet application.global.properties
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
37 | |
10 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
2 | |
2 |