Rename Application Role Command

Use the renameapproles command to upload a JSON file containing information about the application roles that you want to rename for a specific server instance.

You run the renameapproles command through a launcher script, datamodel.sh on Linux and datamodel.cmd on Windows.

If the domain is installed in default folder then the location of the launcher script looks like the following:

Oracle_Home/user_projects/domains/Domain_Name/bitools/bin/datamodel.sh or datamodel.cmd on Windows.

If the client install doesn't have domain names, the launcher script location is as follows:

Oracle_Home\bi\bitools\bin\datamodel.cmd

See What You Need to Know Before Using the Command and Overview of User and Application Role Commands.

Note that if you rename an application role in Oracle BI repository (RPD) and Oracle BI Presentation Catalog (WEBCAT), make sure that both the old role and the new role are present in Enterprise Manager.

Syntax

The renameapproles command takes the following parameters:

renameapproles -T inputfile.json[-L plugin list] -SI service instance -U cred username[-P cred password] [-S hostname] [-N <port number] [-SSL] [-H]

Where

T specifies the name of the JSON input file containing the application role name changes for the server instance.

SI specifies the name of the service instance.

L specifies a single plugin to run or to reverse the default plugin processing order. The plugins determine where the system applies the updates: to the repository, the Oracle BI Presentation Catalog, or both. See Overview of User and Application Role Commands.

The following options are for L:
  • RPD: Specify this option to rename application roles in the repository, only.

  • WEBCAT: Specify this option to rename application roles in the Oracle BI Presentation Catalog. For example, you must use the -L WEBCAT option when renaming application roles in the Oracle BI Presentation Catalog.

  • WEBCAT,RPD: Specify this option to reverse the default plugin run order.

    The default plugin run order is Oracle BI repository (RPD) and then Oracle BI Presentation Catalog (WEBCAT).

  • Omit this option to run the plugins in their default order, which is Oracle BI repository (RPD) and then Oracle BI Presentation Catalog.

U specifies a valid user's name to be used for authentication.

P specifies the password corresponding to the user's name that you specified for U. If you don't supply the password, you're prompted for the password when the command is run. Oracle recommends that you include a password in the command only if you're using automated scripting to run the command.

S specifies the host name. Only include this option when you're running the command from a client installation.

N specifies the port number. Only include this option when you're running the command from a client installation.

SSL specifies to use SSL to connect to the Oracle WebLogic Server to run the command. Only include this option when you're running the command from a client installation.

H displays the usage information and exits the command. Use -H or run .sh without any parameters to display the help content.

Example

datamodel.sh renameapproles -T approlenames.json -SI bi -U weblogic -P password -S server1.example.com -N 7777 -SSL

Creating a JSON Rename Application Role Input File

Use the following syntax to create the JSON rename application role input file.

{
    "Title":"Target Application Roles",
    "App-Roles":[
          { "oldname":"<current_approle1>", "newname":"<new_approle1>" },
          { "oldname":"<current_approle2>", "newname":"<new_approle2>" },
          { "oldname":"<current_approle3>", "newname":"<new_approle3>" }
   ]
}