Novell Doc: ConsoleOne 1.3.x User Guide - Creating RBS Objects for Custom Applications

5.4 Creating RBS Objects for Custom Applications

Typically, administration applications that use RBS objects add the needed objects to your eDirectory tree automatically during installation. However, if your organization has developed a custom administration application that uses RBS objects, you can create the needed RBS objects manually. The following are the types of RBS objects you can create:

Object Type	Container or Leaf	Purpose	Example
Module	Container	Represents a module of the administration application, so that the application's tasks can be logically contained and uniquely identified.	An application might have User and Server modules that each contain a Create task.
Task	Leaf	Represents a specific application function.	Reset Login Password.
Scope	Leaf	Represents the scope in which a role member can exercise the functions of the role, if the application defines scope in non-eDirectory terms. NOTE:Before you can create a scope object, its class must exist in the schema of your eDirectory tree. A scope class is a subclass of RBS:External Scope.	An application that defines scope in Domain Name Service (DNS) terms might let you create scope objects such as: com_xyz com_xyz_usa com_xyz_usa_ny
Role	Leaf	Represents an administrative role. It lists the particular application tasks that role members can perform. See Section 5.2, Defining RBS Roles to create this object type.	For a User Administration application, you might create roles such as: Rights Manager Password Administrator Employment Data Entry

In This Section

5.4.1 Creating an RBS Module Object

Right-click the organization or organizational unit that you want to create the RBS module object in > click New > click Object.
Under Class, select RBS:Module > click OK.
In Name, enter a name for the module.

Be sure to follow proper eDirectory naming conventions. See “ Naming Conventions” in the Novell eDirectory Administration Guide.

Example: User Administration Module

Depending on how the administration application will use the module object, complete the appropriate steps:

Application Will Read the Object to Determine How to Invoke the Actual Module?	Steps
No	Click OK. You're done creating the module object.
Yes	Select Define Additional Properties > click OK. On the Information page, specify the module's URL and software type if they are needed by the application. On the Path page (Role Based Services tab), list any other modules required for execution of this module. Click Help for details. Click OK.

5.4.2 Creating an RBS Task Object

Right-click the RBS module container that you want to create the RBS task object in > click New > click Object.
Under Class, select RBS:Task > click OK.
In Name, enter a name for the task.

Be sure to follow proper eDirectory naming conventions. See “ Naming Conventions” in the Novell eDirectory Administration Guide.

Example: Reset Login Password

Depending on how the administration application will use the task object, complete the appropriate steps:

Application Will Read the Object to Determine How to Invoke the Actual Task?	Steps
No	Click OK. You're done creating the task object.
Yes	Select Define Additional Properties > click OK. On the Information page, specify the application function (entry point) to be invoked and any parameters to be passed on invocation. Click OK.

5.4.3 Creating an Object That Represents a Non-eDirectory Scope

If the class of object you will create isn't defined yet in the schema of your eDirectory tree, use Schema Manager to define it.

See Defining a Custom Object Class.

IMPORTANT:When completing the Class Creation wizard, be sure to set the Effective Class flag and select RBS:External Scope as the class to inherit from.
Right-click the container that you want to create the scope object in > click New > click Object.
Under Class, select the object class that represents the non-eDirectory scope > click OK.
In Name, enter a name for the scope.

Be sure to follow proper eDirectory naming conventions. See “ Naming Conventions” in the Novell eDirectory Administration Guide.

Example: DNS Scope com_xyz_usa

Depending on how the administration application will use the scope object, complete the appropriate steps:

Application Will Read the Object to Determine the Actual Scope to Enforce?	Steps
No	Click OK. You're done creating the scope object.
Yes	Select Define Additional Properties > click OK. On the property pages, specify the scope information required by the application. Click Help for details on specific pages. Click OK.