Installing/Configuring SSF: Application Server 

...

       1.      Install a security product, such as SAP NetWeaver Single Sign-On, on each application server. Note the name and location of the security product's library.

For more information about installing the security product, see the documentation of the security product.

       2.      Specify the SSF parameters on the application server. You can specify them either in the profile parameters  ssf<x>/... or in the environment variables  SSF<x>_... (as of Release 4.5).

As of Release 4.5B, you can install up to three different security products. This may be necessary if different applications use different security products. Therefore, each product uses its own profile parameter set. Define the parameters for the number of security products that you use. See also Maintaining Application-Specific Information.

The table below shows the application server profile parameters.

SSF Profile Parameters

Parameter	Default	Possible Values
Product 1: ssf/ssfapi_lib Product 2: ssf2/ssfapi_lib Product 3: ssf3/ssfapi_lib	Blank - meaning that the system uses the SAPSECULIB. (See the note below.)	Character string up to 255 characters. Refer to your security product to find out the name and location of this file.
Product 1: ssf/ssf_md_alg Product 2: ssf2/ssg_md_alg Product 3: ssf3/ssg_md_alg	MD5	MD2, MD4, MD5, SHA1, RIPEMD160 Refer to your security product for other possible values.
Product 1: ssf_symencr_alg Product 2: ssf2_symencr_alg Product 3: ssf3_symencr_alg	DES-CBC	DES-CBC, TRIPLE-DES, IDEA Refer to your security product for other possible values.
Product 1: ssf/name Product 2: ssf2/name Product 3: ssf3/name	Product 1: SSF Product 2: SSF2 Product 3: SSF3	Character string up to 10 characters (case-sensitive).

When an application server is started, the system always loads the security product SAPSECULIB and assigns its information to the next available ssf<x>/...parameter set.

As default, the system searches for the SAPSECULIB library (libssfso) in the directory specified by the profile parameter DIR_LIBRARY. If necessary, you can specify a different file name and location of the SAPSECULIB library in the corresponding ssf<x>/ssfapi_lib parameter (or in the environment variable SSF<x>_LIBRARY_PATH). If you do, make sure that the corresponding parameter ssf<x>/name (or the environment variable SSF<x>_NAME) contains the name SAPSECULIB.

       3.      To record SSF activites for trace functions, set the SSF_TRACE_LEVEL environment variable to one of the following values:

SSF Trace Levels

Trace level	The system records:
0	·        The starting of the SSF RFC server ·        The loading of the SSF library ·        The installation of the RFC-enabled SSF functions
1	·        Level 0 trace information ·        The name and return code of SSF functions that are called
2	·        Level 0 and 1 trace information ·        Signer and receiver information when SSF functions are called
3	·        Level 0, 1, and 2 trace information ·        All input and output data when SSF functions are called

The system records the trace information in the file dev_ssf<#> (where # is a number assigned to each trace file).

       4.      Perform any application-specific tasks that may be required. For more information, see the application's documentation.