Nortel Networks AS 5300 manual Comma separated strings, Fully qualified user name

Page 20

20Using the Bulk Provisioning Tool

Comma separated strings

Provisioning method syntax can include a string of comma-separated variables. For example, the following is the syntax for the addAdmin provisioning method:

addAdmin using ([The Admin user name,Password,Admin First Name,Admin Last Name,Admin Status,Admin Email Address,Office Phone Number,Home Phone Number,Cell Phone Number,Pager Number,Fax Number,Voicemail Number,VPN Number,System defined role,Time Zone,Locale,Provisioning Role,[The list of Domains that he is assigned to, .. ,The list of Domains that he is assigned to]]) file <file name> [optional] into <file name>

Follow the required format when invoking the provisioning method from the BPT command line or using a file. If nothing appears between two commas, the associated field in the database is not updated. For example, the following addAdmin provisioning method contains minimal administrator information, but still requires the commas to denote the blank fields: addAdmin using

([newguy,mysecret,John,Edwards,Active,,,, ,,,,,Default

Admin,,English,Devices only,[yourcompany.com]]).

Fully qualified user name

Some methods require a fully qualified user name—a user name that is complete with the domain name (for example, joe@mydomain.com). This information is available in the Provisioning Client field descriptions.

Success indication on remove methods

Some BPT provisioning methods can remove data, and return an indication of success even if the data did not preexist in the database. This mirrors the functionality of the database. A success indication for a remove provisioning method, indicates that the associated data no longer exists in the database.

When possible, BPT provisioning methods provide additional indication (in the form of an error message) regarding specific data elements (domain and devices) that are not preexisting in the database when the remove method is invoked. These messages appear on the BPT screen.

For example, if the domain nn.com does not exist, an invocation of removeUser using (jimbob@nn.com) returns an error indication of Invalid Data: Domain Not found ’nn.com’, because the domain is not valid.

If the domain is valid and the user is not preexisting, then a success indication is returned, because the user is not configured on the system.

Nortel AS 5300

Nortel Application Server 5300 Application Programming Interfaces Reference

NN42040-110 01.01 Standard

11 June 2008

Copyright © 2008 Nortel Networks

Image 20
Contents NN42040-110 Legal Notice Contents Starting the Bulk Provisioning Tool New in this release Other changesNew in this release Introduction NavigationAudience Related documentsIntroduction Application Programming Interface fundamentals Open Provisioning Interface fundamentalsWhy use the Bulk Provisioning Tool Bulk Provisioning Tool fundamentalsBulk Provisioning Tool requirements Following table lists the requirements to run the BPTApplication Programming Interface fundamentals BPT main menu Using the Bulk Provisioning ToolInstall and launch the BPT BPT main menu Quit BPT provisioning methods BPT files and scriptsNavigation FilesMethod and file syntax conventions BPT conventions and examplesScripts Optional syntax BracketsAngle brackets GetSysRoles optional into file nameSquare brackets BarSuccess indication on remove methods Comma separated stringsFully qualified user name Define the new provisioning role Unknown error messagesCreate and manage provisioning roles using the BPT AddRole using file D\prov\addexample.txt GetRole using AddExampleAdd the new provisioning role View the new provisioning roleDelete the new provisioning role BPT Help option Help addRoleBPT limitations BPT mapping to the Provisioning ClientBatch processing Resource useProvisioning data visibility Using the Bulk Provisioning Tool Security Using the Open Provisioning InterfaceSecurity, authentication, and authorization WS-Security UsernameToken AuthenticationHttp Basic Authentication Onboard Authentication Special note for .NET authentication headers Authorization Domain-level authorization Provisioning-level authorizationThird-party client development Get the WsdlGenerate stubs WsdlImplement interface accessing stubs Access stubs from the third-party applicationStarting the Bulk Provisioning Tool Starting the Bulk Provisioning ToolLaunching the BPT on a workstation Procedure StepsDownloading the Bulk Provisioning Tool to a workstation Launching the BPT on a workstation Starting the Bulk Provisioning Tool Creating OPI clients Creating Open Provisioning Interface clientsPrerequisites for creating OPI clients Task flow for creating OPI clients Retrieving the error codes Downloading the Axis toolkitConfiguring the class path \axis-14\webapps\axis\WEB-INF\libDownloading the Wsdl file Compiling the client stubs\opiclient Loadname/wsdl/opi\opi\service Writing a client to perform some specific OPI operationsExample Writing a client Writing a client to perform some specific OPI operations Compiling the client class Accessing the OPI Java docs Procedure StepsAdminAuthentication subfolder in the OPI Java Docs folder Writing a client to perform some specific OPI operations Accessing the OPI Java docs Keytool -list -v -keystore opitruststore Importing a CA Certificate into the BPTTool prompts Trust this certificate? no Importing a CA Certificate into the BPT Page Nortel AS
Related manuals
Manual 92 pages 3.24 Kb