Show TOC

Creating Admin Studio InstancesLocate this document in the navigation structure

Use

An admin studio instance is a page that includes the admin studio foundation iView, and the admin studio basic layout.

The following figure shows the parts of an admin studio instance using the default Portal Content admin studio instance, which is part of the Content Administration role:

Each part of an admin studio instance is rendered by a different iView:

An admin studio page can contain the following iViews:

  • Message Area: Displays admin studio messages

  • Search: Enables searching for objects in the Portal Catalog

  • Browse: Displays the Portal Catalog as a tree

  • Favorites Objects: Displays the user's favorite portal objects as a tree

  • Work Container: The container that displays wizards and work unit.

  • Detailed View: Displays the structure of a selected unit object as a tree; for a best fit role, displays the logical structure of the role

All of the iViews, except the Detailed View available out-of-the-box only in the content admin studio, are contained in the admin studio page template, located at:

Start of the navigation path Portal Content Next navigation step Content Provided by SAP Next navigation step  Admin Interfaces Next navigation step  Admin Page Templates Next navigation step  Admin Studio Default Page End of the navigation path.

The PCD path to the admin studio page template is portal_content/com.sap.pct/admin.templates/pages/com.sap.portal.admin_studio_page

Procedure

You can create your own admin studio instance by running an XML Content and Actions script that does the following:

  1. Creates a delta link to the admin studio page template.

    You can also do this manually by creating a delta link from the template.

  2. Configures the new studio by modifying PCD properties in order to specify the following:

    • Entry Points: Specifies the top-level nodes to be displayed in the Portal Catalog. You can choose to show only the Portal Content folder, or only the Business Objects folder, or only the GPAL repositories.

      For PCD-related entry points, you can also specify which types of portal objects to display or not to display.

    • Actions: Specifies the menu items to display when an administrator right-clicks an object in the Portal Catalog.

      You can specify which wizard and work unit to run when the action is selected.

    • Toolbar Actions: Specifies the menu items to display in the work unit toolbar when administrator opens a work unit of a portal object.

    • Startup Actions: Specifies the actions that are automatically selected when the admin studio instance is opened.

    • Action Providers: Specifies sets of standard actions to be included in the admin studio. For example, you can specify that the cut, copy and paste actions for working with portal objects be included. The value is the name of the Web Dynpro component that provides the actions.

More information: XML Script for Admin Studio Configuration