Versions Compared

Old Version 9

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version 10

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table 9-11 Elements for the User permissions summary 

Element

...

Description
user-

...

name

The user we wish to generate the permissions summary for. If this parameter is not specified, the permissions summary will be generated for the user activating this command according to the i3-user parameter.

Mandatory: Yes

output-

...

file

The file the command output will be written to. If this parameter is not specified the output will be written as follows:

...

  • An xml file will be generated under the following folder: infra\cli2\permissions.

...

  • The file name will be of the following format: permissions_summary_YYYY.MM.DD_HH_MM_S S.xml.

Mandatory: No

Command output

The user permissions summary is printed to an output file as described above in the Parameters specification section.

Output format

The output xml structure will be as follows:

<user-permissions-summary user-name="user-name">
     <roles-permissions-summary>
          <role role-name="role-name">
               <permission>
               <description>permission description</description>
               <permission-type>permission type</permission-type>
               <permission-operation>permission operation</permission-operation>
               <resource resource-type="resource type" [resource-information] />
               <affected-instances>
               <instance>
               <instance-name>instance name</instance-name>
               <server-name>instance server name</server-name>
               <technology-code>instance technology</technology-code>
               </instance>
               …additional instances
          </affected-instances>
          </permission>
          …additional permissions
     </role>
     …additional roles
     </roles-permissions-summary>
</user-permissions-summary>

Output specification

...

  • User-name

...

  • . The name of the user this summary was generated for

...

  • Role-name

...

  • . The name of a role assigned to this user

...

  • Permission. Role’s permission specification

...

  • Description. The description of this permission

...

  • Permission-type

...

  • . The permission type

...

  • Permission-operation

...

  • . The permission operation

...

  • Resource. The resource this permission was granted on

...

  • Resource-type

...

  • . The type of the Resource-type can have one of the following values: technology, application, Tier or instance

...

  • Resource-information

...

  • . See resource information definitions in Table 9-3 on page 111.

...

  • Affected-instances

...

  • . The list of instances derived from the resource the permission was granted on (i.e. if the resource is the ‘Default’ application all the instances connected to the ‘Default’ application will be listed here)

...

  • Instance-name

...

  • . The name of the instance

...

  • Server-name

...

  • . The name of the server the instance is installed on

...

  • Technology-code

...

  • . The technology code of the instance
Example

This is an example of a permissions summary file for user ‘usr1’ with roles that contains the following permissions:•    MONITOR

  • MONITOR.VIEW on the ‘Default’ application

...

  • ADMINISTRATE.FULL_CONTROL on an SQL Server instance

...

  • MONITOR.EXECUTE on ‘SQL Server’ Tier in the ‘Default’ application

<user-permissions-summary user-name="usr1">
     <roles-permissions-summary>
          <role role-name="monitor default environment" role-scope="ENVIRONMENT"

...


               <permission>
               <description>'Monitor.View' permission on the selected applications</description>
               <permission-type>MONITOR</permission-type>
               <permission-operation>VIEW</permission-operation>
               <resource resource-type="ENVIRONMENT" environment-name="Default" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               <instance>
               <instance-name>H47_TEST</instance-name>
               <server-name>poolhp3</server-name>
               <technology-code>SP</technology-code>
               </instance>
               <instance>
               <instance-name>H47_TEST2</instance-name>
               <server-name>poolhp3</server-name>
               <technology-code>SP</technology-code>
               </instance>
               </affected-instances>
               </permission>
          </role>
          <role role-name="monitor sql apptier" role-scope="APPTIER">
               <permission>
               <description>'Monitor.View' permission on the selected Tiers</description>
               <permission-type>MONITOR</permission-type>
               <permission-operation>VIEW</permission-operation>
               <resource resource-type="APPTIER" environment-name="Default" apptier-name="SQL Server" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               </affected-instances>
               </permission>
               <permission>
               <description>'Monitor.Execute' permission on the selected Tiers</description>
               <permission-type>MONITOR</permission-type>
               <permission-operation>EXECUTE</permission-operation>
               <resource resource-type="APPTIER" environment-name="Default" apptier-name="SQL Server" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               </affected-instances>
               </permission>
          </role>
          <role role-name="administrate sql instance" role-scope="INSTANCE">
              <permission>
               <description>'Administrate.Execute' permission on the selected instances</description>
               <permission-type>ADMINISTRATE</permission-type>
               <permission-operation>EXECUTE</permission-operation>
               <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               </affected-instances>
               </permission>
               <permission>
               <description>'Administrate.Full Control' permission on the selected instances</description>
               <permission-type>ADMINISTRATE</permission-type>
               <permission-operation>FULL_CONTROL</permission-operation>
               <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               </affected-instances>
               </permission>
               <permission>
               <description>'Administrate.View' permission on the selected instances</description>
               <permission-type>ADMINISTRATE</permission-type>
               <permission-operation>VIEW</permission-operation>
               <resource resource-type="INSTANCE" instance-name="PIFA1000" server-name="pifa1000" technology-code="SQ" />
               <affected-instances>
               <instance>
               <instance-name>PIFA1000</instance-name>
               <server-name>pifa1000</server-name>
               <technology-code>SQ</technology-code>
               </instance>
               </affected-instances>
               </permission>
          </role>
     </roles-permissions-summary>
</user-permissions-summary>

 

Precise. Performance intelligence from click to storage. Learn more > >

...