Connector Guides › Connectors Guide › Sample Connector › Implementing the Connector

Implementing the Connector

Perform the following steps to transform the sdkscript connector into the sdkuposcript connector:

In the sdkdyn metadata

1. Add the following connector level attribute definitions.
   1. managedEndpoint (eTDYN-bool-01) – Used to configure the operational mode of an endpoint.
   2. useSendMailExit (eTDYN-bool-02) – Used to indicate that the SendMail program exit is invoked by the UPO exits.
   3. useLogExit (eTDYN-bool-03) – Used to indicate that the Logging program exit is invoked by the UPO exits.
   4. mailserver (eTDYN-str-03) – Specifies the host name of the mail server that the SendMail exit connects to.
   5. mailrecipient (eTDYN-str-04) – Specifies the email address that the SendMail sends the mail to.
   6. mailsender (eTDYN-str-05) – Specifies the email address that the SendMail exit uses as the sender.
2. Add the following account level attribute definition in the sdkdyn metadata.
   1. requestStatus (eTDYN-int-01) – This indicates the status of the request. This attribute definition is used mainly to receive the completed status of the request.
3. Define the program exits.

   Two program exits are provided as samples. The SendMail exit gets the mail related connector level attributes and sends the message passed to it by the UPO exit. The mail subject is also passed to it by the invoking UPO exit. The code can be changed to include CC recipients if required.

   The Logging exit writes the details of the request to a file, in a sub-directory of that specified by eTDYNConnectionURL.

4. Define the UPO exits.

   One function is defined for each UPO exit. Where there are similarly named exits, a suffix is added indicating the operational mode where that exit is used, so there are functions such as ADD_ACCOUNT_NONMANAGED, ADD_ACCOUNT_MANAGED, ENABLE_ACCOUNT, and so forth.

   The non-managed mode exit functions package the request details in XML, which are made as similar as possible to the data block generated by the UPO connector. This xml block is then passed to the SendMail or Logging program exits, if so configured.

   The managed mode exit functions perform the provisioning operations as in the sdkscript connector.

5. Re-structure the code of the functions specified in the opbindings.

   Whereas with sdkscript, the provisioning operations are performed right in the body of the opbindings functions, the sdkuposcript functions first check the operational mode of the endpoint, then invoke the appropriate UPO exit.