Defining Logon Data 
Purpose
You have the option of defining logon data to control system access at the receiver systems.
Some end point types require logon data to be specified. The end point type of the receiver business system determines whether logon data must be specified or not.
The end point for the RFC adapter requires logon data, for example.
You can choose whether you want to use logon data or anonymous log on for the following end point types:
· End point for an Integration Engine and end point for an Integration Engine for Acknowledgments (for URL addressing)
· End point for the HTTP adapter (for URL addressing)
· End point for other XI connections (XI Connectivity) (for URL addressing)
When addressing using an HTTP destination, the logon data is already defined in the destination for these end point types.
Logon data for an end point for an IDoc adapter is already defined by using an RFC destination and does not need to be specified explicitly.
Features
The logon data for a receiver business system is contained in one configuration object and defined at configuration time. The Integration Builder provides you with various tools for performing the following tasks.
· Display an Overview of Logon Data
