Creating a Portal Tenant 
Use
You use the Tenant Management tool in the portal to create a tenant.
It is not possible to create sub-tenants (nesting a tenant within a tenant).
Prerequisites
· You are logged on to the portal as a super administrator.
When a tenant is created, certain permissions in the Portal Catalog are automatically assigned and modified; therefore, only an administrator with Owner permission for the entire Portal Catalog, such as a super administrator, can create the portal tenant.
A system administrator is sufficient when later maintaining an existing tenant.
· You have defined and configured a unique portal tenant system for a tenant (see Creating a Portal Tenant System).
Procedure
1. In the portal, navigate to System Administration ® Multitenant Portal. The Tenant Management screen is displayed (see Managing Portal Tenants).
2. In the Portal Tenant Systems area, enter the friendly name of the unique portal system you created for the tenant and click Search.
§ The search string is case sensitive.
§ You can use a wildcard character (*), if needed. For example, to display all tenant systems defined in the portal, enter *. To display all systems beginning with Accounting, enter Accounting*.
The results of your search are displayed below the search area.
3. Choose the relevant portal tenant system in the search results list. The fields in the Create/Edit Tenant area become editable and the name of the selected system is displayed in the System Name field.
4. In the Create/Edit Tenant screen, provide values for the following properties (mandatory properties are marked by an asterisk):
Property |
Description |
Tenant Name1 |
Enter the name of the tenant. The name must be unique. It should not exceed 20 characters and can include letters (a-z, A-Z), digits (0-9), and an underscore (_). No spaces are allowed.
If you are a global administrator working with tenant-specific portal roles, always enter the tenant name as the prefix of the portal role in lower-case characters, regardless of how you defined the tenant name when you created it. This requirement is not valid for users, groups, and UME roles. For example, the portal role content_admin in TenantA is identified as tenanta\content_admin, whereas user smithj in TenantA, is identified as TenantA\smithj. |
Description |
Enter descriptive information about the tenant. |
Logon Ticket for Client1 |
Enter the same client number for the logon ticket as that of the client of the ABAP system that the tenant uses for its user information. This is a unique three-digit number to be written in the logon ticket for users of that tenant. For more information, see Single Sign-On with Logon Tickets.
Client number 000 is not allowed. This client number is reserved for the portal. |
Portal URL Alias |
Enter a unique portal URL alias to be used by users of the tenant for logging on to the tenant’s portal. The alias must begin with portal/. For example, if you enter portal/tenanta, the complete portal URL used by a tenant user in this case, would be: http://<server>:<port>/irj/portal/tenanta |
Logo2,3 |
Enter a relative or absolute path to the upper customized branding image to be displayed in the portal logon screen when a user logs on to this portal tenant. For example
(relative PCD path): |
Brand Name2,3 |
Enter a relative or absolute path to the lower customized branding image to be displayed in the portal logon screen when a user logs on to this portal tenant. For example
(relative PCD path): |
Stylesheet Path2,3 |
Enter a relative or absolute path to the stylesheet to be used by the logon screen when a user logs on to this portal tenant. For example
(relative PCD path): Note that the look and feel of certain elements in the logon screen are still controlled by the stylesheet of the default portal theme. |
System Name1 |
Specifies the friendly name of the unique portal tenant system defined for the tenant. |
1 These properties are not editable after the portal tenant has been created (see Editing Portal Tenants).
2 Requires that you have uploaded a PAR file containing the customized image. For more information on how to create a PAR with branding images and defining the necessary PCD path, see Configuring Customized Logon Screens for Tenants.
3 If you leave this property blank, the default SAP NetWeaver logon images or stylesheet will be used instead.
5. Select Save.
Result
When you save the tenant, the following takes place:
...
1. The tenant is added to the Tenants area in the Tenant Management screen.
2. In the UME, a unique virtual group for the tenant is generated.
3. A new Portal Catalog folder with the name of the tenant is automatically created in the Portal Content/Tenants folder. For example: Portal Content/Tenants/TenantA.
4. In the tenant's new folder, three subfolders (Content, Role, and Desktop) are automatically created.
5. A content administrator, user administrator, and standard end user role are automatically created for the tenant in the new Role folder.
Note the following:
¡ If you intend to use the new tenant-specific user administration and content administrator roles, you need to assign them to tenant users.
¡ Users defined in the tenant's ABAP client are automatically assigned to the new standard end user role, so there is no need to assign them manually.
6. Portal permissions are automatically assigned to the tenant's new folders, other folders in the Portal Catalog, and to security zones.
7. The portal checks the connection to the ABAP user store and registers the tenant in the UME cache.
8. In the tenant's system object, properties listed in the Tenant category are updated to enable connectivity to the backend client of the ABAP user store.
For detailed information about the aforementioned initial folders, roles, group, and permissions, see Initial Folders, Content, and Permissions for Tenants.
You can now begin assigning portal content, delegating administration tasks, and assigning users to tenant roles.