Writing a new application or change an existing application

You are ready to begin including the server specific code that enables your Calendar application to participate in an single signon environment. Using your previous programming experience with EIM APIs, you create a program flow similar to this one:

Application Initialization
- EIM Get Handle
- EIM Connect
Processing Loop
- Wait for user request
- Authenticate user using Kerberos
- Call EIM to map from network authentication service user to Local user
- Swap to local user
- Perform Task
- Swap back to original user
- Go to "Wait for user request"
  
  This scenario assumes that you have already created or changed the client specific code to enable your application for an i5/OS^® single signon environment, and therefore only provides the steps required to complete the server specific part of your program.
Application Termination
- Destroy EIM Handle

See the ISV code examples for example pseudocode and snippets that you can use to help complete the server specific part of your program. When you have added the necessary client and server specific code to your Calendar application, you can create a single signon test environment to test it.

Parent topic:

Scenario: Enabling single signon for ISV applications

Previous topic: Completing the planning prerequisite worksheet

Next topic: Creating a single signon test environment