At run-time, the adapter does the following:

1. Loads the JavaScript from the ResourceAction corresponding to the current provisioning action.

2. Prepares the necessary Java input objects to make available to the JavaScript.

3. Invokes the JavaScript.

4. Processes the result returned (or exceptions and errors) from the JavaScript.

   The $WSHOME/sample/ScriptedHost/ScreenSampleActions.xml file contains a set of sample resource action definitions that could be used to provision users to a theoretical screen-based host application. You will need to customize these definitions to your application.

   The Scripted Host adapter supports end-user scripting for the following provisioning actions:

   Action	Description	Required?
   create	Create a new user.	No, but if not provided, users cannot be created.
   delete	Delete an existing user.	No, but if not provided, users cannot be deleted.
   disable	Disable an existing user.	No, but if not provided, users cannot be disabled.
   enable	Enable an existing user.	No, but if not provided, users cannot be enabled.
   getAccountIterator	Return an object used to perform iteration of existing users.	No, but if neither getAccountIterator nor listAll is provided, account iteration cannot be performed.
   getUser	Fetch attributes for an existing user.	Yes.
   login	Login to application.	Yes.
   logoff	Logoff application.	Yes.
   listAll	Return a list of existing user IDs.	No, but if neither getAccountIterator nor listAll is provided, account iteration cannot be performed.
   update	Update attributes for an existing user.	No, but if not provided, users cannot be updated.

   Every action script receives an actionContext map, as defined by the java.util.Map class. The possible contents of the map vary for each action. The following sections describe each action, and provide the following information about the action:

   • Context. Describes the set of entries available in the actionContext map added into the Javascript execution context by the adapter before the script executes.

   • Error Handling. Notes describing how the script is expected to handle abnormal or error conditions

   For additional information about the actions listed in the previous table, see the following sections:

   • create Action

   • delete Action

   • disable Action

   • enable Action

   • getAccountIterator Action

   • getUser Action

   • listAll Action

   • login Action

   • logoff Action

   • update Action