SAP Connector 5.9 Additional Configuration | MuleSoft Documentation
# SAP Connector 5.9 Additional Configuration
After you complete basic SAP Connector configuration, you can perform additional configuration tasks, such as changing advanced settings and defining extended properties.
## Configure General Settings
  1. At the bottom of the canvas, click **Global Elements**.
  2. Click **Create**.
  3. Expand **Connector Configuration** , select either **SAP Inbound** or **SAP Outbound** , and click **OK**.
  4. Click the **Advanced tab** at the top of the **Global Element Properties** screen:
  5. In the **General** section, to set the **Max Idle time** parameter:
    1. Select **Expiration policy**.
    2. Enter a value in the **Max Idle time** , and then add the **Time Unit**.


Field | Type | Description | Default Value  
---|---|---|---  
**Expiration Policy** |  ExpirationPolicy |  Configures the minimum amount of time that a dynamic configuration instance can remain idle before the runtime considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. The runtime purges the instances when appropriate.  
**Max Idle time** |  A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it’s considered eligible for expiration.  
Enumeration one of:
  * HOURS
  * MICROSECONDS
  * MILLISECONDS
  * MINUTES
  * NANOSECONDS SECONDS

  
## Configure Advanced Settings
You can set encoding, version, flag, format, and timeout parameters in Advanced settings.
To change these field values, click the **Advanced tab** at the top of the **Global Element Properties** screen:
Field | XML Attribute | Description | Default Value  
---|---|---|---  
**Display Name** |  Set a reference name for the endpoint used internally by the Mule configuration.  
Set a canonical name for an encoding. See Oracle’s supported encodings.  
**Default IDocument Version** |  `defaultIdocumentVersion` |  Set the version when sending an intermediate document (IDoc). Values for the IDoc version correspond to `IDOC_VERSION_xxxx` constants in `com.sap.conn.idoc.IDocFactory`.  
**Disable Function template cache flag** |  `disableFunctionTemplateCacheFlag` |  Set to disable the function template cache.  
**Evaluate response flag** |  `evaluateResponseFlag` |  Set if an error response should throw an exception or let the user handle it with another result.  
**Log trace flag** |  `logTraceFlag` |  Set if the trace should be logged on the Mule server.  
**Use SAP format** |  `useSAPFormat` |  Set to use the SAP default format when working with business application programming interface (BAPI) functions using a synchronous remote function call (sRFC).  
## Define Extended Properties
Extended properties enable you to tune SAP outbound configuration parameters.
To define extended properties for the SAP connector global element:
  1. Navigate to the **Advanced** tab on the **General** pane:
  2. Locate the **Extended Properties** section at the top of the window.
  3. Select the **Edit inline** option.
  4. Click **+** to add a new extended property. Use the same property name that SAP uses:
    1.     2. Target System configuration


### Configure the Client Environment
Configure the system variables that depend on the operating system you are using, and generate the PSE (personal security environment):
  1. Use the following command to open your cmd or terminal and unpack the SAPCAR and SAP Cryptographic Library:
`SAPCAR –xvf <name_of_the_file.SAR>
This extracts files from the folder **(which folder?)**
  2. Configure the following environment variables: **(Do the variables vary by OS or are they the same and just configured differently?)** * For this example, the path to the library is “C:\Users\Administrator\Desktop\SNC”:*
     * SNC_LIB
     * SECUDIR = `<Path_to_library>`
     * LD_LIBRARY_PATH = `<Path_to_library>\sapcrypto.dll`
     * SSF_LIBRARY_PATH = `<Path_to_library>\sapcrypto.dll`
For Windows, the `sapcrypto.dll` 64bit version must be in another path and added to a new variable called SNC_LIB_64.
In your cmd or terminal, use the following command to create the PSE:
`sapgenpse gen_pse -v -p RFC.pse`
When you run this command, you must enter a password or PIN to use later and a distinguished name, which must be unique. You can check for names that are already used at STRUST.
  3. Add the credentials that your session user needs to access the PSE which will create the file cred_v2 with this command: sapgenpse seclogin -p RFC -O you_user.


## Next
Now that you have completed configuration, you can experiment with the SAP Examples.
## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center