maximo 7.5 multi tenancy db2

Maximo Asset ManagementVersion 7.5

Multitenancy Beta

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 99.

References in content to IBM products, software, programs, services or associated technologies do not imply that they willbe available in all countries in which IBM operates. Content, including any plans contained in content, may change at anytime at IBM's sole discretion, based on market opportunities or other factors, and is not intended to be a commitment tofuture content, including product or feature availability, in any way. Statements regarding IBM's future direction or intentare subject to change or withdrawal without notice and represent goals and objectives only. Please refer to thedeveloperWorks terms of use for more information.

© Copyright IBM Corporation 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Multitenancy systemoverview . . . . . . . . . . . . . . 1Applications and options available for the betarelease . . . . . . . . . . . . . . . . 2The multitenancy system provider . . . . . . . 2

The configuration administrator . . . . . . . 3Tenants . . . . . . . . . . . . . . . . 3

Tenant data in a multitenancy database . . . . 4

Chapter 2. Configuring a multitenancysystem . . . . . . . . . . . . . . . 5Configuring multitenancy . . . . . . . . . . 5Configuring WebSphere Application Server formultitenancy . . . . . . . . . . . . . . 5Enabling multitenancy for your product . . . . . 6Configuring template data . . . . . . . . . . 6

Configuring a template tenant administrationsecurity group . . . . . . . . . . . . . 7

Chapter 3. Administering a multitenancysystem . . . . . . . . . . . . . . . 9System properties in a multitenancy system . . . . 9

ACCESSTYPE domains . . . . . . . . . 11VALUERULES domain . . . . . . . . . 11System properties for new tenants . . . . . . 12Setting multitenancy system properties . . . . 12

Domains in a multitenancy system . . . . . . 13Domains overview . . . . . . . . . . . 13

Applications associated with domains . . . 14Domains and organizations or sites . . . . 15Types of domains . . . . . . . . . . 16

Working with domains as the configurationadministrator . . . . . . . . . . . . . 19

Adding alphanumeric domains . . . . . . 20Associating domain values with conditions . . 29Creating synonyms of internal values. . . . 29Deleting synonyms of internal values. . . . 31Deleting domains . . . . . . . . . . 31

Working with domains as the system provider oras a tenant user . . . . . . . . . . . . 32

Adding alphanumeric domains . . . . . . 32Associating domain values with conditions . . 41Creating synonyms of internal values. . . . 41Deleting synonyms of internal values. . . . 43Deleting domains . . . . . . . . . . 43

Crontasks in a multitenancy system . . . . . . 44Reports in a multitenancy system . . . . . . . 44Bulletin boards in a multitenancy system . . . . 44

Chapter 4. Managing tenants . . . . . 47Adding tenants . . . . . . . . . . . . . 47

Activating and disabling tenant accounts . . . . 48Modifying tenants . . . . . . . . . . . . 48Adding tenant users . . . . . . . . . . . 48Communicating with tenants using the bulletinboard . . . . . . . . . . . . . . . . 49

Chapter 5. Modules and applications 51Database Information application . . . . . . . 51

Adding an attribute to an application. . . . . 51Rules for modifying attributes . . . . . . . 52Defining a lookup map . . . . . . . . . 53Adding system messages . . . . . . . . . 53

Chapter 6. Multitenancy reference . . . 55Template data tables . . . . . . . . . . . 55Master data tables . . . . . . . . . . . . 57Multitenancy system properties. . . . . . . . 59

Asset properties . . . . . . . . . . . . 62Attached document properties . . . . . . . 62Automation scripts properties . . . . . . . 66Bidirectional language properties . . . . . . 66Bulletin board property . . . . . . . . . 67Calendar property . . . . . . . . . . . 67Classification item properties . . . . . . . 67Communication template property . . . . . 67Condition property . . . . . . . . . . . 67Cron task properties . . . . . . . . . . 68Database properties. . . . . . . . . . . 68Deployed assets property . . . . . . . . . 74Email interaction properties . . . . . . . . 74Email listener properties . . . . . . . . . 76Environment properties . . . . . . . . . 76E-signature properties . . . . . . . . . . 77General ledger property . . . . . . . . . 78Inventory property . . . . . . . . . . . 78Issues and transfers property . . . . . . . 78Lightweight Directory Access Protocol integrationproperties . . . . . . . . . . . . . . 78maximo.properties file . . . . . . . . . . 79Migration Manager properties . . . . . . . 80mxe.help properties . . . . . . . . . . 82OSLC properties . . . . . . . . . . . . 83Reorder property . . . . . . . . . . . 84Report integration properties . . . . . . . 84Security properties . . . . . . . . . . . 88Server properties . . . . . . . . . . . 91Utilities for logging and testing. . . . . . . 95Work order generation property . . . . . . 96

Notices . . . . . . . . . . . . . . 99Trademarks . . . . . . . . . . . . . . 100

© Copyright IBM Corp. 2012 iii

iv IBM Maximo Asset Management: Multitenancy Beta

Chapter 1. Multitenancy system overview

Multitenancy systems provide software to multiple client organizations from asingle, shared instance of the software. This means that multiple distinct usersaccess the same database instance. The multitenancy system is owned andmanaged by a multitenancy system provider, the system provider. Clientorganizations that sign up to use a multitenancy system are called tenants. Datathat belongs to one tenant is isolated from all other tenant data in the system.

Example

This is an example of a simple multitenancy system.

Table 1. Multitenancy system provider and tenants in a simple multitenancy system

Tenantname

TenantID

Tenantlanguage

Database username

Tenant Admin username Users

Multitenancysystemprovider

1000 English LANDLORDDB LL_SYSADMIN John

TenantCompanyOne

1200 French tenantonedb tt1admin Maria, Anne

TenantCompanyTwo

1300 Spanish tenanttwodb tt2dbadmin Gustavo, Sarah

The provider user, John, adds Tenant Company One and Tenant Company Two tothe system, by creating two tenant records in the Tenants application.

The Tenant Admin user for Tenant Company One, tt1admin, creates the users,Maria and Anne, by adding them in the Users application.

When Maria accesses the system, she uses a combination of her user name,password, and the Tenant ID for Tenant Company One to login. She can only seeand modify the data for Tenant Company One. She cannot see any data thatbelongs to Tenant Company Two. She accesses the database using the tenantonedbuser name. The user interface is shown in French. When Maria runs reports, thereport contains data only for Tenant Company One.

Sarah, a user in Tenant Company Two adds a value to a master table. Only usersfrom Tenant Company Two can use the value. The value is not available to usersfrom Tenant Company One.

“Applications and options available for the beta release” on page 2As a IBM® Maximo® Asset Management user, there are some new applicationsavailable to you in this beta release. You should be aware that someapplications and some options within applications that are available in a typicaldeployment of Maximo Asset Management are not available for themultitenancy beta release. For more information on the applications and optionsthat are not available, check the posting in the beta forum.“The multitenancy system provider” on page 2An organization that provides multitenancy software is called the multitenancysystem provider (the system provider). The system provider manages thesoftware for the client organizations.

© Copyright IBM Corp. 2012 1

“Tenants” on page 3Client organizations that sign up to use a multitenancy system are calledtenants. Tenants are added to the multitenancy system by the multitenancysystem provider. Every tenant is associated with a tenant identifier (tenant ID).Users of the multitenancy system are generally employees of the clientorganization.

Applications and options available for the beta releaseAs a IBM Maximo Asset Management user, there are some new applicationsavailable to you in this beta release. You should be aware that some applicationsand some options within applications that are available in a typical deployment ofMaximo Asset Management are not available for the multitenancy beta release. Formore information on the applications and options that are not available, check theposting in the beta forum.

New and changed applications

Database configuration application and the Database information applicationThe database configuration application is available to the configurationadministrator. It is not available to tenants. As a tenant user, you haveaccess to the Database information application. Using this application, youcan view information about database objects and attributes, for example,field lengths, and attribute names. You can also manage system messagesand make limited changes to attributes. Learn more...

Tenants applicationThe multitenancy system provider can manage tenant information in theTenants application. Learn more...

Parent topic: Chapter 1, “Multitenancy system overview,” on page 1

The multitenancy system providerAn organization that provides multitenancy software is called the multitenancysystem provider (the system provider). The system provider manages the softwarefor the client organizations.

The system provider is a special type of tenant and is associated with a tenantidentifier. Users who are associated with the provider tenant code access thesystem with a combination of their tenant code, user name, and password. Theprovider has access to the Tenant Administration application, to some systemadministration data, and to certain tenant level properties.

The provider can create tenants, modify tenant details, and enable and disabletenants. However, the provider cannot access tenant user accounts and or see theworking data of tenants.

“The configuration administrator” on page 3The multitenancy system provider administers and maintains the tenanttemplate data. The system provider uses the configuration administrator tenantto administer the initial data that is added to the database when a tenant iscreated.

2 IBM Maximo Asset Management: Multitenancy Beta

Parent topic: Chapter 1, “Multitenancy system overview,” on page 1

The configuration administratorThe multitenancy system provider administers and maintains the tenant templatedata. The system provider uses the configuration administrator tenant toadminister the initial data that is added to the database when a tenant is created.

The configuration administration tenant is a special tenant reserved for the systemprovider. The system provider can log in as the configuration administrator tenantto administer the initial data that is added to the database when a tenant iscreated, including setting initial, default values for domains and system properties.The configuration administrator tenant can change the template data.

There is a security group reserved for the configuration administration tenant.Users with this security group access are authorized to administer non-templatedata.Parent topic: “The multitenancy system provider” on page 2Related tasks:“Configuring template data” on page 6When a tenant record is added to the multitenancy system, an area of the databaseis isolated for the tenant’s data. The database area is populated with template dataand delta storage data. The system provider can configure and modify the initialtemplate data using the configuration administrator tenant.“Working with domains as the configuration administrator” on page 19As the configuration administrator, you can configure default value lists anddomain values. These values will be populated as part of the template data createdfor new tenants. You use domains to choose values associated with specific fields.The lists of defined values are known as domains (sometimes referred to as valuelists). The system uses many domains in its applications.Related reference:“Template data tables” on page 55Tables that are copied and added to the database when a tenant is created.“Master data tables” on page 57Specific tables that contain data that is shared by all tenants. Tenants can add datato these tables. This additional data is flagged with the tenant ID for that tenant,and is stored as delta data.

TenantsClient organizations that sign up to use a multitenancy system are called tenants.Tenants are added to the multitenancy system by the multitenancy systemprovider. Every tenant is associated with a tenant identifier (tenant ID). Users ofthe multitenancy system are generally employees of the client organization.

Tenant users require a combination of their user name, password, and tenant ID toaccess the multitenancy system. They can operate only within their own tenantcontext. Users can view and modify only the data that is associated with theirtenant ID. In addition, users must use the database connection that is associatedwith the database user for their tenant ID.

A tenant user cannot switch to another tenant context by entering another tenantID. The users of one tenant can never view or modify the data that belongs toanother tenant whether the data is in the database or in memory.

Chapter 1. Multitenancy system 3

Tenant information is managed in the Tenant Administration application.

When a tenant is created, an area of the database is isolated for the tenant’s data.The database area is populated with template data and delta storage data.

“Tenant data in a multitenancy database”When a tenant is created, an area of the database is isolated for the tenant’sdata. The database area is populated with system data, template data, andmaster data.

Parent topic: Chapter 1, “Multitenancy system overview,” on page 1Related tasks:“Adding tenant users” on page 48You can add users to the multitenancy system. Each user is associated with onetenant code. The user name must be unique within the associated tenant code.

Tenant data in a multitenancy databaseWhen a tenant is created, an area of the database is isolated for the tenant’s data.The database area is populated with system data, template data, and master data.

When the provider creates a tenant record, the database is populated with thefollowing initial data for the tenant:

System data tablesThe standard system data tables do not have the tenant identifier (tenantID) column.

Master data tablesMaster data tables contain data that is shared by all the tenants. If a tenantadds their own information to a row in the master tables, the tenant ID isadded to the table row. The information is available for that tenant only.For example, tables that contain ALN domain values are shared by alltenants. However, if a tenant adds an ALN domain value, a row is addedto the table to contain the value. The tenant ID of that tenant is added tothe row. Only the tenant that added the value can access the value.

Template data tables.Template data tables contain data that is unique for each tenant and thatcan be modified by each tenant. Template data tables have the tenant IDcolumn. When a tenant is created table rows with the tenant ID of the newtenant are created in the template data tables. A tenant can view andmodify only the information that is associated with the tenant ID of thattenant.

Parent topic: “Tenants” on page 3Related tasks:“Configuring template data” on page 6When a tenant record is added to the multitenancy system, an area of the databaseis isolated for the tenant’s data. The database area is populated with template dataand delta storage data. The system provider can configure and modify the initialtemplate data using the configuration administrator tenant.Related reference:“Template data tables” on page 55Tables that are copied and added to the database when a tenant is created.“Master data tables” on page 57Specific tables that contain data that is shared by all tenants. Tenants can add datato these tables. This additional data is flagged with the tenant ID for that tenant,and is stored as delta data.


Chapter 2. Configuring a multitenancy system

You must complete several configuration tasks to configure your database as amultitenancy database.

Before you begin

Before you enable multitenancy, ensure that you are working in a supportedenvironment. The following environment is supported:v DB2®, version 10.1 or later.v WebSphere® Application Server, version 8 or later.v a version of Maximo Asset Management that supports multitenancy

“Configuring multitenancy”You must configure your DB2 database as a multitenancy database.“Configuring WebSphere Application Server for multitenancy”You must configure your IBM WebSphere Application Server to support amulti-tenant environment. The configuration steps activate FGAC (fine grainaccess control) and trusted context switching.“Enabling multitenancy for your product” on page 6You can enable multitenancy on a previously installed product.“Configuring template data” on page 6When a tenant record is added to the multitenancy system, an area of thedatabase is isolated for the tenant’s data. The database area is populated withtemplate data and delta storage data. The system provider can configure andmodify the initial template data using the configuration administrator tenant.

Configuring multitenancyYou must configure your DB2 database as a multitenancy database.Parent topic: Chapter 2, “Configuring a multitenancy system”

Configuring WebSphere Application Server for multitenancyYou must configure your IBM WebSphere Application Server to support amulti-tenant environment. The configuration steps activate FGAC (fine grain accesscontrol) and trusted context switching.

Procedure1. Using the administrative user ID and password, login to the WebSphere

Application Server console.2. From the console menu, select Server Types > WebSphere application

servers.3. From the Application servers list, select server1.4. In theWeb Container Settings section of the Configuration tab, select Web

Container Transport Chains.5. Create a Web Container Transport Chain, by clicking New and entering the

following properties:


Option Description

Transport chain name MAXIMOTRANSPORT

Port name 9999

6. Click Finish to complete the creation of the transport chain.7. Save your changes.8. From the console menu, select WebSphere application Servers.9. From the Application servers list, select server1.

10. In theServer Infrastructure section of the Configuration tab, expand Java andProcess Management and select Process Definition.

11. In the Additional Properties section of the Process Definition window, selectJava Virtual Machine.

12. Configure the Java virtual machine using the following properties:

Option Description

Initial Heap Size 512

Maximum Heap Size 1024

Generic JVM Arguments -Dsun.rmi.dgc.ackTimeout=1000-Djava.net.preferIPv4Stack=true

13. Save your changes and click OK.14. From the main console window, expand Environment and select Virtual

Hosts.15. Create a virtual host with the Name field set to MAXIMOSERVER, and save your

changes.16. In the Virtual Hosts window, select MAXIMOSERVER

17. In the Additional Properties section of the Virtual Hosts window, select HostAliases.

18. Select New and create a Host Alias. Accept the default values and click OK.19. Select New and create a second Host Alias. Change the port number to 9999

and click OK.20. Save the two Virtual Hosts.21. Build and deploy the maximo.ear file.22. Stop and restart the server.Parent topic: Chapter 2, “Configuring a multitenancy system,” on page 5

Enabling multitenancy for your productYou can enable multitenancy on a previously installed product.Parent topic: Chapter 2, “Configuring a multitenancy system,” on page 5

Configuring template dataWhen a tenant record is added to the multitenancy system, an area of the databaseis isolated for the tenant’s data. The database area is populated with template dataand delta storage data. The system provider can configure and modify the initialtemplate data using the configuration administrator tenant.


About this task

The template data includes data for Sets, Organizations, Deployed Assets, SystemProperties, Database Configuration, Reports, Security Groups, Users, CurrencyCodes.

Procedure1. Using the configuration administrator credentials, log in to the multitenancy

system.2. In the System properties application, specify the system properties.3. Save your changes and refresh.4. In the Database Configuration application, configure the database.5. In the Domains application, set the default values and rules for domains.

“Configuring a template tenant administration security group”Parent topic: Chapter 2, “Configuring a multitenancy system,” on page 5Related concepts:“The configuration administrator” on page 3The multitenancy system provider administers and maintains the tenant templatedata. The system provider uses the configuration administrator tenant toadminister the initial data that is added to the database when a tenant is created.“Tenant data in a multitenancy database” on page 4When a tenant is created, an area of the database is isolated for the tenant’s data.The database area is populated with system data, template data, and master data.Related reference:“Template data tables” on page 55Tables that are copied and added to the database when a tenant is created.“Master data tables” on page 57Specific tables that contain data that is shared by all tenants. Tenants can add datato these tables. This additional data is flagged with the tenant ID for that tenant,and is stored as delta data.

Configuring a template tenant administration security groupParent topic: “Configuring template data” on page 6

Chapter 2. Configuring a multitenancy system 7

Chapter 3. Administering a multitenancy system

As the system provider, after you configure multitenancy for your product, youcan configure the system and the database, and schedule backups to ensure thatyour database is working at optimum performance levels. You can then performfunctions such as setting up organizations and specifying chart of accounts andcurrencies. You can use the configuration administrator tenant to configuretemplate data for new tenants. As a tenant of a multitenancy system, you canconfigure a subset of system settings.

“System properties in a multitenancy system”In a non-multitenancy system, system properties are set at the system level. In amultitenancy system, some properties remain at the system level and areinvisible to tenants. The Configuration Administrator controls the value of theseproperties. The system provider and tenants can modify a subset of the systemproperties to support their needs. There are rules that govern the ways inwhich tenants can modify properties. Tenants can also view some of theproperties that they cannot modify.“Domains in a multitenancy system” on page 13As a tenant or as the system provider, you can add or modify domains to suityour business practices. Domain values that you add or modify are flagged inthe database with your tenant ID. The domain values are only available tousers associated with your tenant ID.“Crontasks in a multitenancy system” on page 44Tenants can run their own instances of crontasks. If one tenant runs a crontaskon one schedule and a second tenant runs the same crontask on a differentschedule, the crontasks will run independently and will not impact each other.“Reports in a multitenancy system” on page 44As the system provider you can administer and run predefined reports. You canalso import new and updated reports to the multitenancy system. As a tenantuser you can run the set of reports delivered by the system provider.“Bulletin boards in a multitenancy system” on page 44In a multitenancy system, tenant users can create bulletin board messages. Theycan specify the audience for the messages from within users of the same tenant.In addition, the system provider can use the bulletin board to broadcastmessages to all tenants.

System properties in a multitenancy systemIn a non-multitenancy system, system properties are set at the system level. In amultitenancy system, some properties remain at the system level and are invisibleto tenants. The Configuration Administrator controls the value of these properties.The system provider and tenants can modify a subset of the system properties tosupport their needs. There are rules that govern the ways in which tenants canmodify properties. Tenants can also view some of the properties that they cannotmodify.

The Configuration Administrator can set properties at system level. Theseproperties are used when the master template data is created, for example, when atenant is added to the system.


The system provider can modify some properties to tailor the system to supporttheir business needs. The system provider can modify more properties than atenant can. Tenants have access to a limited set of properties, they can change thevalues from the default values to support their implementation. Tenants can viewthe master value of a property or their own modification of the property value. Atenant cannot view a property value modified by another tenant. The ACCESSTYPEdomain value controls the types of user that can see and modify a property. TheVALUERULES domain value controls how a property can be modified.

Any properties set by tenants or by the system provider are refreshed on theirsystem by live refresh. Themaximo.properties file cannot be modified by tenants orthe system provider.

If tenants modify a master property value set by the Configuration Administratorthen that value is associated with the Tenant ID of the tenant. The information isavailable for that tenant only.

In some cases, the master value set by the Configuration Administrator cannot beused by all tenants, for example, a contact email address. These tenant-specificproperty values are collected as part of the tenant registration process.

“ACCESSTYPE domains” on page 11Every system property in a multitenancy system is associated with anACCESSTYPE value. The ACCESSTYPE value of the system propertydetermines which users can see the property, and which users can modify theproperty.“VALUERULES domain” on page 11Every system property is associated with an VALUERULES value. The VALUERULESdomain is a synonym domain that contains the rules for modifying systemproperty values.“System properties for new tenants” on page 12The initial system properties for all new tenants are part of the initial templatedate and are set by the configuration administrator. However, there are systemproperties that are unique for each tenant, for example, the tenant’s contactemail address. These properties have an ACCESSTYPE value of type 3. Whenthe tenant is created, these values for these properties are added by the systembased on information supplied by the tenant.“Setting multitenancy system properties” on page 12A system property is a key-value pair that is used at the system level. You canset system properties that various components use to control how applicationsand other aspects of the product work. Which properties you can set andmodify depend on your role and is controlled by the ACCESSTYPE of theproperty. You use the System Properties application to manage systemproperties and the values of the system properties that various components use.


Parent topic: Chapter 3, “Administering a multitenancy system,” on page 9Related reference:“Multitenancy system properties” on page 59The configuration administrator sets the system level properties that are used astemplate data for the tenants. The Configuration administrator can modify allsystem properties. The system provider and tenant users can modify a limitednumber of system properties to tailor the system to support their needs.

ACCESSTYPE domainsEvery system property in a multitenancy system is associated with anACCESSTYPE value. The ACCESSTYPE value of the system property determineswhich users can see the property, and which users can modify the property.

Table 2. ACCESSTYPE domain values and descriptions

Value Description

0 Data with this value is visible to all tenants in the system. However, onlythe Configuration Administrator can modify this data.

1 Data with this value is visible only to the Configuration Administratorand the System provider. However, only the Configuration Administratorcan modify this data. The VALUERULES attribute for this data is visible toall tenants. The VALUERULES attribute can be modified by theConfiguration Administrator.

2 All data with this value is visible to all tenants in the system. TheConfiguration Administrator sets the default values for this data. TheVALUERULES attribute for this data is visible to all users. The VALUERULESattribute can be modified by the Configuration Administrator. Anytenant can modify the property value, however the modification mustadhere to the defined value rules for that property.

3 Data with this value can be modified by individual tenants to supporttheir implementation. here is no default value for this data. The data canbe set in the Tenants application. When a tenant is created, the systemadds default values to these properties based on information given bythe tenant.

Parent topic: “System properties in a multitenancy system” on page 9Related reference:“System properties for new tenants” on page 12The initial system properties for all new tenants are part of the initial template dateand are set by the configuration administrator. However, there are systemproperties that are unique for each tenant, for example, the tenant’s contact emailaddress. These properties have an ACCESSTYPE value of type 3. When the tenantis created, these values for these properties are added by the system based oninformation supplied by the tenant.

VALUERULES domainEvery system property is associated with an VALUERULES value. The VALUERULESdomain is a synonym domain that contains the rules for modifying systemproperty values.

Table 3. VALUERULES domain values and descriptions

Value Description

ONONLY This property can only be enabled.

OFFONLY This property can only be disabled.

Chapter 3. Administering a multitenancy system 11

Table 3. VALUERULES domain values and descriptions (continued)

Value Description

INCONLY The value of this property can only be increased.

DECONLY The value of this property can only be decreased.

Parent topic: “System properties in a multitenancy system” on page 9

System properties for new tenantsThe initial system properties for all new tenants are part of the initial template dateand are set by the configuration administrator. However, there are systemproperties that are unique for each tenant, for example, the tenant’s contact emailaddress. These properties have an ACCESSTYPE value of type 3. When the tenantis created, these values for these properties are added by the system based oninformation supplied by the tenant.

Table 4. Source of the default values for system properties that are unique to each tenant

Property Default value

mxe.adminEmail TENANTREG.PRIMARYEMAIL

mxe.adminPasswd

mxe.adminusercredential Null

mxe.adminuserid TENANTREG.LOGINID

mxe.adminuserloginid TENANTREG.LOGINID

mxe.int.adminfromemail TENANTREG.PRIMARYEMAIL

mxe.int.admintoemail TENANTREG.PRIMARYEMAIL

mxe.int.dfltuser TENANTREG.LOGINID

mxe.system.regpassword autogenerate

mxe.system.reguser ‘MAXREG’

mxe.workflow.admin TENANTREG.LOGINID

Parent topic: “System properties in a multitenancy system” on page 9Related concepts:“ACCESSTYPE domains” on page 11Every system property in a multitenancy system is associated with anACCESSTYPE value. The ACCESSTYPE value of the system property determineswhich users can see the property, and which users can modify the property.

Setting multitenancy system propertiesA system property is a key-value pair that is used at the system level. You can setsystem properties that various components use to control how applications andother aspects of the product work. Which properties you can set and modifydepend on your role and is controlled by the ACCESSTYPE of the property. You usethe System Properties application to manage system properties and the values ofthe system properties that various components use.

About this task

As the Configuration Administrator, you can modify any system property.

As the system provider or as a tenant, you can modify system properties that havethe ACCESSTYPE values of 2 or 3. Changes are applied using Live refresh. This


means that the property value takes effect immediately after saving the value.

Procedure1. In the System Properties application, select the system property that you want

to modify.2. Modify the value. The modifications that you make are governed by your role,

the ACCESSTYPE value of the property and the VALUERULE value of the property.3. Select Live refresh to apply your changes.Parent topic: “System properties in a multitenancy system” on page 9Related reference:“Multitenancy system properties” on page 59The configuration administrator sets the system level properties that are used astemplate data for the tenants. The Configuration administrator can modify allsystem properties. The system provider and tenant users can modify a limitednumber of system properties to tailor the system to support their needs.

Domains in a multitenancy systemAs a tenant or as the system provider, you can add or modify domains to suit yourbusiness practices. Domain values that you add or modify are flagged in thedatabase with your tenant ID. The domain values are only available to usersassociated with your tenant ID.

“Domains overview”You can add domains or modify existing ones to fit with your businesspractices. After adding domains, additional tasks might be required, dependingon the domain and how you want the system to display it. As the multitenancysystem provider, you can configure default value lists and domain values.These values will be populated as part of the template data created for newtenants. As a tenant user, you can add and remove values and rules in domainsto meet the business needs of your organization.“Working with domains as the configuration administrator” on page 19As the configuration administrator, you can configure default value lists anddomain values. These values will be populated as part of the template datacreated for new tenants. You use domains to choose values associated withspecific fields. The lists of defined values are known as domains (sometimesreferred to as value lists). The system uses many domains in its applications.“Working with domains as the system provider or as a tenant user” on page 32You use domains to choose values associated with specific fields. The lists ofdefined values are known as domains (sometimes referred to as value lists). Thesystem uses many domains in its applications. The default domain values areset by the configuration administrator. As a the multitenancy system provideror as a tenant user, you can add and remove values and rules in domains tomeet the business needs of your organization.

Parent topic: Chapter 3, “Administering a multitenancy system,” on page 9

Domains overviewYou can add domains or modify existing ones to fit with your business practices.After adding domains, additional tasks might be required, depending on thedomain and how you want the system to display it. As the multitenancy systemprovider, you can configure default value lists and domain values. These valueswill be populated as part of the template data created for new tenants. As a tenantuser, you can add and remove values and rules in domains to meet the businessneeds of your organization.


“Applications associated with domains”After you create a domain, you need to apply the domain to an attribute. Youuse the Classifications, the Database Configuration, and the ApplicationDesigner applications to apply and to modify domains after you have createdthem.“Domains and organizations or sites” on page 15Applying domains to the organization or site level (by typing appropriatevalues in the organization field and site field) might create unintentional accessrestrictions. Leaving these fields blank is the default, and stores domains at thesystem level.“Types of domains” on page 16Some fields are associated with Select Value lists from which you can choose anappropriate value. The lists of defined values are known as domains (sometimesreferred to as value lists).

Parent topic: “Domains in a multitenancy system” on page 13

Applications associated with domainsAfter you create a domain, you need to apply the domain to an attribute. You usethe Classifications, the Database Configuration, and the Application Designerapplications to apply and to modify domains after you have created them.

The table that follows lists the applications that are used to apply or to modifydomains.

Table 5. Applications used to apply or to modify domains

Application Description Example

Classifications Associate a domain with anattribute in the Attributestable window.

Database Configuration Associate a domain with anattribute.

Most domains also have adefault value, which youwould specify in DatabaseConfiguration. If the attributeis required, a default valuefor the domain is alsorequired.

An amount field might bebound to a NUMERICdomain or a status fieldmight be bound to aSYNONYM domain.

When you configure thedatabase, the system doesnot validate the value youinsert as the default fieldvalue. For example, you canhave an Organization calledEAGLENA, where the onlyacceptable domain value isCREW4.

You can make the crewidattribute required in thePreventive Maintenanceapplication, give it thedefault value of CREW2, andconfigure the databasewithout error. The error, suchas CREW2 is not a validvalue, appears only whenyou return to the PreventiveMaintenance application toinsert a record.


Table 5. Applications used to apply or to modify domains (continued)

Application Description Example

Application Designer Modify the user interface asneeded.

If you added an ALNdomain for a field, you addthe select value button usingthe application designerapplication. NewCROSSOVER domains mightrequire new fields in thedestination application.

Parent topic: “Domains overview” on page 13

Domains and organizations or sitesApplying domains to the organization or site level (by typing appropriate valuesin the organization field and site field) might create unintentional accessrestrictions. Leaving these fields blank is the default, and stores domains at thesystem level.

Example one

When you specify an organization or site for domain values, note where thedomain is being used.

In the Labor application, you use the SKILLLEVEL domain on the CRAFTSKILLobject. You specify both the organization and site values for domain values. Whenyou access the Labor application and lookup the skill level, you do not see yourvalues. This issue occurs because you specified a site, and the object that is usingthe domain is at the organization level. To fix this problem, remove the site fromthe domain value.

Example two

You might want to leave the organization field and site field empty for all values(users in all organizations and sites can access them). If you specify anorganization or site for one value, you must specify an organization or site for allvalues (users in the specified organizations or sites can access them).

Otherwise, complicated outcomes can result. For example, you can set anorganization with the following domain values:

Table 6. Sample domain setup with specific organizations

Value Organization

GREEN A

BLUE B

RED (No organization specified)

With the domain configuration above, you get the following results:v Records in Organization A can access GREEN only.v Records in Organization B can access BLUE only.v Records in other organizations (other than Organization A and Organization B)

can access RED only.



Types of domainsSome fields are associated with Select Value lists from which you can choose anappropriate value. The lists of defined values are known as domains (sometimesreferred to as value lists).

You can work with the following types of domains:

ALN A list of alphanumeric values.

CrossoverA special table domain in which the system brings back another value (orvalues) from the specified record.

NumericA list of numeric values.

Numeric rangeA list of numeric values that you define by specifying a range.

SynonymThese are special, reserved domains in the system. You cannot add ordelete synonym domains. You can add new synonym values that arepresented to the user.

Table A list of values generated from a table.

Internal and non-internal domains

Some domains are used by the business logic of the system. These domains arecalled internal domains.

If you attempt to edit an internal domain, you encounter the following restrictions:v You can modify only the description of the internal domain and internal domain

values.v You cannot add or delete a row of values from an internal domain.v You cannot delete an internal domain.

“ALN domains” on page 17ALN domains are simple lists of values that use one of the alphanumeric datatypes.“Crossover domains” on page 17Crossover domains return a value from a field in one application to a field inanother application. For example, you can return the serial number of an assetin the Assets application to a field in the Item Master application.“Numeric range domains” on page 17A numeric range domain is a domain that uses one of the numeric data types,but for which you specify a range rather than specific values.“Synonym domains” on page 18Synonym domains are special domains that are reserved by the system. Youcannot add new synonym domains, but you can add new synonym values thatare presented to the user.“TABLE domains” on page 19TABLE domains are dynamic sets of values based on the values of anotherobject.


“Foreign keys and TABLE domains” on page 19Using domains, you can create a foreign key from a system level for site-levelor for organization-level objects.


ALN domains:

ALN domains are simple lists of values that use one of the alphanumeric datatypes.

Example

If your company requires that calendar information is consistent, you can create alist of the days of the week or months of the year. Unlike a SYNONYM domain,the values in this list are for informational purposes only, the values are noteditable.Parent topic: “Types of domains” on page 16

Crossover domains:

Crossover domains return a value from a field in one application to a field inanother application. For example, you can return the serial number of an asset inthe Assets application to a field in the Item Master application.

When you create a crossover domain, you can specify one or more conditions thatmust be met before values are returned from a source object. You can defineconditions for the source object and the destination object, and if the conditions aremet, values are returned to the destination field. You use the ConditionalExpression Manager to define conditions for crossover domains.

Order of fields and conditions on crossover domains

If you define conditions on crossover domains in custom applications, carefullyconsider the order that users scan through the fields. When you define a condition,the condition is evaluated at the moment the value for the attribute is set. If acondition relates to another field with a value that has not been set, values are notreturned as expected. For example, this situation might occur due to the order ofthe layout of the application interface.

Example: Serial number crossover

You want to add a serial number (the destination) to a work order. You want theserial number to cross over from the serial number of the related asset, the source,when the work type is emergency maintenance, the condition. Select the work typebefore you select the asset number for the crossover to occur as expected.Parent topic: “Types of domains” on page 16

Numeric range domains:

A numeric range domain is a domain that uses one of the numeric data types, butfor which you specify a range rather than specific values.

You can specify the following kinds of ranges:


DiscreteA range with a defined interval between values, for example, a range from0 to 10, with valid values 0, 2, 4, 6, 8, and 10. The interval in this exampleis 2.

ContinuousA range within which any value that satisfies the data type is valid. Forexample, in a range of 1 to 6 with a decimal data type and scale of 2,values such as 1, 1.03, 2.14, 3, 4.73, 5.2, and 6 are all valid. The interval inthis example is null (no value in the Interval field).

You cannot create lookups for numeric range domains. Therefore, consider thetypes of values a user or automated process normally enter into a field with theirtype of domain. An invalid value results in an error message.

Numeric ranges with more than one segment

You might use multiple segments in your numeric range domain for variousreasons. Here are two examples:v You want to define a measurement range that is more precise at low

measurements than at high measurements and that correspond with meterreadings. You can define three segments:Segment 1: minimum 0, maximum 0.8, interval 0.2, resulting valid values, 0, 0.2,0.4, 0.6, 0.8Segment 2: minimum 1, maximum 9, interval 1, resulting valid values 1, 2, 3, 4,5, 6, 7, 8, 9Segment 3: minimum 10, maximum 30, interval 5, resulting valid values 10, 15,20, 25, 30

A user or automated process would always enter one of those values.v You want values inserted into a field only if the reported values are beyond the

accepted normal range. For example, meter readings could be above or belowthe accepted tolerances. You can define two segments:Segment 1: minimum 0, maximum 9.9, interval null. Any reading between 0 and9.9 could be entered.Segment 2: minimum 20.1, maximum null, interval null. Any reading of 20.1 orhigher could be entered.

Meter readings from 10 and 20 would not be recorded.Parent topic: “Types of domains” on page 16

Synonym domains:

Synonym domains are special domains that are reserved by the system. You cannotadd new synonym domains, but you can add new synonym values that arepresented to the user.

An example of a synonym domain is work order status. The system has severalvalues to reflect status: APPR (Approved), CAN (Canceled), CLOSE (Closed),COMP (Completed), WAPPR (Waiting on Approval), and others. Each work orderstatus has an internal value, used by the system in its business rules, and a valuethat users see and choose from. You cannot add a new internal value. You can adda synonym, the value that is presented to the user.


Example: Synonym values for WAPPR (Waiting on Approval)

Suppose your company procedure requires two people to approve a work order.You could add synonym values for the internal WAPPR value. You could thenpresent two different values to the user, for example, WAPPRMAN and WAPPRVP,to represent approvals at the manager and vice president level.Parent topic: “Types of domains” on page 16Related tasks:“Creating synonyms of internal values” on page 29You can create synonyms of internal values so that you can present different valuesto users based on your business needs.“Deleting synonyms of internal values” on page 31You can delete a synonym of an internal value when it is no longer useful.

TABLE domains:

TABLE domains are dynamic sets of values based on the values of another object.

Example

You can use a TABLE domain to present a valid list of records from the PERSONtable to be typed in the OWNER field on a record.Parent topic: “Types of domains” on page 16

Foreign keys and TABLE domains:

Using domains, you can create a foreign key from a system level for site-level orfor organization-level objects.

Example

If you want to add a new attribute for assets on the TKTEMPLATE object, performthe following steps:1. Create a TABLE domain.2. Add the assetnum attribute to the TKTEMPLATE.3. Add a relationship to the asset table.4. Add the attribute siteid to TKTEMPLATE.Parent topic: “Types of domains” on page 16

Working with domains as the configuration administratorAs the configuration administrator, you can configure default value lists anddomain values. These values will be populated as part of the template data createdfor new tenants. You use domains to choose values associated with specific fields.The lists of defined values are known as domains (sometimes referred to as valuelists). The system uses many domains in its applications.

“Adding alphanumeric domains” on page 20You add an alphanumeric (ALN) domain when you want to add a domain thatuses one of the alphanumeric data types.“Associating domain values with conditions” on page 29You can associate domain values with a condition to limit the number of valuesavailable to users for certain conditions such as statuses, priorities, and assets.This association ensures that only users determined by you can set certainstatuses, change the priority of work orders, and so on.


“Creating synonyms of internal values” on page 29You can create synonyms of internal values so that you can present differentvalues to users based on your business needs.“Deleting synonyms of internal values” on page 31You can delete a synonym of an internal value when it is no longer useful.“Deleting domains” on page 31You can delete most domains when they are no longer useful.

Parent topic: “Domains in a multitenancy system” on page 13Related concepts:“The configuration administrator” on page 3The multitenancy system provider administers and maintains the tenant templatedata. The system provider uses the configuration administrator tenant toadminister the initial data that is added to the database when a tenant is created.

Adding alphanumeric domainsYou add an alphanumeric (ALN) domain when you want to add a domain thatuses one of the alphanumeric data types.

About this task

Because you can use a domain with multiple fields, the length you specify must beless than or equal to the length of the shortest field with which you intend to usethe domain. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less. If you specify a length greaterthan the field the domain is used in, you cannot assign the domain to the attributein the Database Configuration application. Alternatively, you can specify a greaterlength in the Domains application and use the Database Configuration applicationto change the length of the field that uses the domain.

Procedure1. Open the Domains application.2. At the bottom of the Domains table window, click Add New Domain and

select Add New ALN Domain.

3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. In the Length field, specify a length that is equal to or less than the length of

the field that uses the domain. For example, if you are adding a domain for afield in the Assets application that has a length of 12, then specify a length of12.

7. Click New Row.8. Fill the Value and Description fields.9. Optional: Apply a domain value to a specific organization or site by entering

the relevant values in the Organization and Site fields. Domains are appliedat the system level by default.You can leave the Organization and/or Site fields empty for all values so thatusers in all organizations and sites can access them. Or you could specify anorganization and/or site for all values so that only the users in the specifiedorganizations and/or sites can access them. Otherwise, complicated outcomescan result.For example, if you enter a value RED with no organization specified, a valueGREEN with Organization A specified, and a value BLUE with Organization B


specified, then records in Organization A has access to GREEN only. Recordsthat are in Organization B has access to BLUE only. Records that are in otherorganizations has access to RED only. When you specify an organizationand/or site for one value, records in that organization and/or site no longerhave access to values that have no organization or site specified.

10. Optional: Click New Row again to add more values.11. Click OK.

What to do next

After you add a domain, you might still have several tasks to perform, dependingon the domain and how you want to display it.

In the Classifications application, you associate a domain with an attribute in theAttributes table window. No further configuration is needed.

If you use a domain in any other context, adding a domain requires additionaltasks:v Associate the new domain with an attribute in the Database Configuration

application.v Configure the database in the Database Configuration application.v Use the Application Designer application to modify the user interface as needed.

For example, if you add an ALN domain for a field, you must add the selectvalue button. New crossover domains might require new fields in thedestination application.“Adding crossover domains”You add a crossover domain when you want to add a domain that returns avalue from a field in one application to a field in another application.“Adding numeric domains” on page 23You add a numeric domain when you want to add a domain that uses one ofthe numeric data types.“Adding numeric range domains” on page 25You add a numeric range domain when you want to add a domain that usesone of the numeric data types. However, you specify a range rather thanspecific values.“Adding table domains” on page 27You add a table domain when you want to add a domain that draws its valuesdirectly from a column in the database. This process creates a dynamic valuelist because the values it draws from the database might change.

Parent topic: “Working with domains as the configuration administrator” on page19Related concepts:“Numeric range domains” on page 17A numeric range domain is a domain that uses one of the numeric data types, butfor which you specify a range rather than specific values.

Adding crossover domains:

You add a crossover domain when you want to add a domain that returns a valuefrom a field in one application to a field in another application.


About this task

Ensure that the SQL statements that you use in this procedure are valid. Theapplication does not validate SQL statements.

Procedure

1. Open the Domains application.2. In the Domains table window, click Add New Domain and select Add New

CROSSOVER Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Crossover Domain table window, click New Row.6. Define details for the crossover domain:

Field Description

Object Select the name of the object that containsthe attribute that you want to create adomain from. For example, to obtain valuesfrom the ASSET object, select ASSET.

Validation Where Clause If the value to be validated by this domainis considered valid, type the part of theclause that when queried against the objectin the Object field returns at least onerecord.

For example, if you want a field named Z(attribute Z) to contain values from theassetnum field in the Assets application, youwould type: ASSETNUM = :Z (the colonrepresents the bind variable).

List Where Clause Type the part of the clause that specifies thevalue that you want to select based on thevalidation WHERE clause.

For example, to select asset records thatbegin with the numbers 114, type ASSETNUMLIKE '114%'

7. Optional: Specify a group value and a key value to select an error message todisplay when domain validation fails. You define values for error messages inthe Database Configuration application.a. In the Error Message Group field, specify the group value of the error

message.b. In the Error Message Key field, specify the key value of the error message.

8. Optional: To apply a domain to a specific organization or site, specify valuesin the Organization and Site fields. To allow access to users in allorganizations and sites, clear all values from these fields.

9. Select fields for the crossover domain:a. In the Crossover Fields table window, click New Row.b. In the Source Field list, select an attribute of the object that you specified

in the Object field. This attribute represents the field from which you wantto return values.

c. In the Destination Field text box, specify the field to which you wantvalues to be returned.


d. Optional: Select the Accept NULL Value check box to copy the value fromthe source field when the value of the target attribute is empty. Thisfunction overwrites the previous value.

e. Optional: Select the No Overwrite check box if you want to copy the valueof the source attribute when it is null.

10. Optional: Specify conditions for the source object or the destination object, orboth:a. In the Condition on Source field, select a condition or use the Conditional

Expression Manager to build the condition for the source object of thecrossover. The source object must meet the condition before the crossoveroccurs.

b. In the Condition on Destination field, select a condition or use theConditional Expression Manager to build the condition for the destinationobject of the crossover. The destination object must meet the conditionbefore the crossover occurs.

c. In the Sequence field, type a numeric value to specify the order that thecrossover occurs when multiple crossovers are defined. Crossovers withlower values occur before crossovers with higher values.

11. Click OK to add the crossover domain to the database.

What to do next


In the Classifications application, you associate a domain with an attribute in theAttributes table window, and no further configuration is needed.



For example, if you add an ALN domain for a field, you must add the selectvalue button. New crossover domains might require new fields in thedestination application.

Parent topic: “Adding alphanumeric domains” on page 20Related concepts:“Crossover domains” on page 17Crossover domains return a value from a field in one application to a field inanother application. For example, you can return the serial number of an asset inthe Assets application to a field in the Item Master application.

Adding numeric domains:

You add a numeric domain when you want to add a domain that uses one of thenumeric data types.

About this task

Because you can use a domain with multiple fields, the length that you specifyhere must be less than or equal to the length of the shortest field with which you


use the domain. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less for the domain. If you specify alength greater than the field the domain is used in, you are not able to assign thedomain to the attribute in the Database Configuration application. Alternatively,you can specify a greater length in the Domains application. You can use theDatabase Configuration application later to change the length of the field that usesthe domain.

Procedure

1. Open the Domains application.2. At the bottom of the Domains table window, click Add New Domain and

select Add New NUMERIC Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. Depending on the data type the Length field might or might not be editable.

If editable, specify a length that is equal to or less than the length of the fieldthat uses the domain. For example, if you are adding a domain for a field inthe Assets application that has a length of 12, then specify a length of 12.

7. For Decimal data type only, in the Scale field, specify a scale value if differentfrom the default, 2.

8. Click New Row.9. Fill the Value and Description fields.

10. Optional: Apply a domain value to a specific organization or site byspecifying values in the Organization and Site fields. Domains are applied atthe system level by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify an organization and/or site for all values so that only users inthe specified organizations and/or sites can access them. Otherwise,complicated outcomes can result.For example, if you enter a value 100 with no organization specified, a value300 with Organization A specified, and a value 500 with Organization Bspecified, then records in Organization A have access to 300 only. Records thatare in Organization B have access to 500 only. Records that are in otherorganizations have access to 100 only. Once you specify an organizationand/or site for one value, records in that organization and/or site no longerhas access to values that have no organization/site specified.


What to do next



If you use a domain in any other context, adding a domain requires additionaltasks:


v Associate the new domain with an attribute in the Database Configurationapplication.

v Configure the database in the Database Configuration application.v Use the Application Designer application to modify the user interface as needed.


Parent topic: “Adding alphanumeric domains” on page 20Related concepts:“Numeric range domains” on page 17A numeric range domain is a domain that uses one of the numeric data types, butfor which you specify a range rather than specific values.

Adding numeric range domains:

You add a numeric range domain when you want to add a domain that uses oneof the numeric data types. However, you specify a range rather than specificvalues.

About this task

Because you can use a domain with multiple fields, the length that you specifyhere must be less than or equal to the length of the shortest field you use thedomain with. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less for the domain. If you specify alength greater than the field the domain is used in, you cannot assign the domainto the attribute in the Database Configuration application. Alternatively, you canspecify a greater length in the Domains application. You can use the DatabaseConfiguration application later to change the length of the field that uses thedomain.

Procedure


select Add New NUMERIC RANGE Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. Depending on the data type, the Length field might or might not be editable.


7. For DECIMAL data type only, in the Scale field, specify a scale value ifdifferent from the default, 2.

8. Click New Row and fill the following fields. Each row defines a range.


Field Description

Range Segment Specify an identifying number for thesegment. For example, 1 if the range has justone segment, or 1, 2, or 3 if the domain hasthree segments.

For a range with regular intervals or asimple continuous range, you need only onesegment.

Range Minimum Specify the lowest value in the range, forexample, 10 in the range 10 to 50.

You can leave either the Range Minimumfield or the Range Maximum field empty(null value), but not both.

Range Maximum Specify the highest value in the range, forexample, 50 in the range 10 to 50.

You can leave either the Range Minimumfield or the Range Maximum empty (nullvalue), but not both.

Interval For a range with discrete values, specify thevalue of the interval that separates thevalues you want to appear in the list. Forexample, the interval is 10 in the range 10 -50 if you want the values 10, 20, 30, 40, and50 to be valid.

For a continuous range of values betweenthe minimum and maximum values, leavethis field null (empty).

Continuous is relative to the data type. Forexample, if the data type is INTEGER andthe range is 1 - 5, then only 1, 2, 3, 4, and 5are valid values.

9. Optional: Apply a domain value to a specific organization or site byspecifying values in the Organization and Site fields. Domains are applied atthe system level by default.You might want to leave the Organization and/or Site fields empty for allrange segments so that users in all organizations and sites can access them. Oryou could specify an organization and/or site for all range segments so thatonly users in the specified organizations and/or sites can access them.

10. Optional: Click New Row again to add ranges for additional segments.11. Click OK.

What to do next



If you use a domain in any other context, adding a domain requires additionaltasks:


v Associate the new domain with an attribute in the Database Configurationapplication.

v Configure the database in the Database Configuration application.v Use the Application Designer application to modify the user interface as needed.


Parent topic: “Adding alphanumeric domains” on page 20Related concepts:“Numeric range domains” on page 17A numeric range domain is a domain that uses one of the numeric data types, butfor which you specify a range rather than specific values.

Adding table domains:

You add a table domain when you want to add a domain that draws its valuesdirectly from a column in the database. This process creates a dynamic value listbecause the values it draws from the database might change.

Procedure


select Add New TABLE Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. Click New Row and fill the following fields.

Field Description

Object Specify the name of the object. The objectyou want is the object containing theattribute from which you want to create adomain.

For example, to obtain values from theASSET object, specify ASSET.

List Where Clause Type the part of the clause that specifies thevalues that you want to select based on thevalidation WHERE clause.

For example, to select asset records thatbegin with the numbers 114, type: assetnumlike '114%'

Attention: The system does not validateyour entry for syntax or any other errors. Besure that you have typed a correct WHEREclause. If you make errors, errors do notbecome apparent until you configure thedatabase.


Field Description

Validation Where Clause If the value to be validated by this domainis considered valid, type the part of theclause that when queried against the objectin the Object field should return at least onerecord.

Usually, the clause involves a bind variablefor the field that uses this domain forvalidation. The bind variable is representedby a colon (:) followed by the field name.

For example, if you want a field named Z(attribute Z) to contain values from theassetnum field in the Assets application,type: assetnum = :z

6. Optional: Specify a group value and a key value to select an error message todisplay when domain validation fails. You define values for error messages inthe Database Configuration application.a. In the Error Message Group field, specify the group value of the error


7. Optional: Apply a domain value to a specific organization or site by specifyingvalues in the Organization and Site fields. Domains are applied at the systemlevel by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify organization and/or site for all values so that only users in thespecified organizations and/or sites can access them.

8. Optional: Click New Row again to add more rows.9. Click OK.

What to do next







Parent topic: “Adding alphanumeric domains” on page 20Related concepts:“TABLE domains” on page 19TABLE domains are dynamic sets of values based on the values of another object.“Foreign keys and TABLE domains” on page 19Using domains, you can create a foreign key from a system level for site-level orfor organization-level objects.

Associating domain values with conditionsYou can associate domain values with a condition to limit the number of valuesavailable to users for certain conditions such as statuses, priorities, and assets. Thisassociation ensures that only users determined by you can set certain statuses,change the priority of work orders, and so on.

Before you begin

Before you associate a domain value with a condition, you must set up the domainvalues for the ALN, synonym, and numeric domains. You must then define acondition for when particular domain values should appear in a domain.

About this task

You can create a condition in the condition library of the Conditional ExpressionManager application. If you modify the condition for a domain value after thevalue has been selected for a field, the existing values are not revalidated. There isno current record on the Search or List pages so conditional values are notsupported on these pages.

Procedure1. Open the Domains application and select the Edit Detail icon for the domain

containing the values you want to associate with a condition. Depending on thedomain type selected, an ALN, numeric, synonym, table, or crossover windowopens from where you can add or change conditions.

2. Add or change the conditions as necessary.3. Optional: If you want to add the same conditions for multiple domain values,

select Set Conditions and select a condition from the condition library. You canapply the same condition to all of the selected values.

4. Optional: If you want domain values to be used by multiple objects, specify theobjects in the Object Name field.

5. Save the record.Parent topic: “Working with domains as the configuration administrator” on page19

Creating synonyms of internal valuesYou can create synonyms of internal values so that you can present different valuesto users based on your business needs.

Procedure1. Open the Domains application.2. Find the synonym domain for which you want to add a synonym value, for

example WOSTATUS.


3. Click Edit Detail. In the Synonym Domain table window, the set of currentvalues: the Internal Value is used by the system and must be unique. The Valueand its description are what users see.

4. Click New Row and enter values in the fields:

Field Description

Internal Value Specify the internal value for which youwant a synonym.

For example, in the WOSTATUS domain, ifyou want to create a synonym for WAPPRcalled WAIT, you would specify the WAPPRinternal value.

Value Specify the synonym value you want a userto see.

For example, WAIT.

Description Type a description of the synonym todifferentiate it from the existing value.

5. Optional: In the Default field, select the check box if you want the system touse the new synonym value by default. Each internal value can have only onedefault synonym value.For example, the system inserts WAPPR (Waiting for Approval) as the statuswhen you create a work order. You add a synonym value, WAIT. If you wantthe system to insert WAIT instead of WAPPR, then make WAIT the default.

6. Optional: Apply a domain value to a specific organization or site by specifyingvalues in the Organization and Site fields. Domains are applied at the systemlevel by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify organization and/or site for all values so that only users in thespecified organizations and/or sites can access them.If you create a synonym value and specify a site or organization, and then clickOK, the system automatically inserts duplicate rows for the other values. Theduplicate rows have the site or organization you specified for the new valuethat you created. For example, the MRTYPE domain has three values:RECURRING, STANDARD, and TRANSFER (each with an internal value of thesame name). If you create a synonym value, REGULAR, with the internal valueof STANDARD and specify Organization B, the system automatically creates(when you click OK) the additional synonym values RECURRING andTRANSFER with Organization B specified.

Important: After you have implemented the system and inserted records, yougenerally must not add a synonym value with a site or organization specified.This action can invalidate existing data. If you must add a synonym value witha site or organization specified, you must also add synonym values for all theexisting values that are in the database. For example, if you added a synonymvalue for STANDARD with an organization or site specified, you must also addsynonym values for RECURRING and TRANSFER (if they have been used onrecords) with the same organization or site specified.

7. Click New Row to add more synonyms.8. Click OK.


Parent topic: “Working with domains as the configuration administrator” on page19Related concepts:“Synonym domains” on page 18Synonym domains are special domains that are reserved by the system. You cannotadd new synonym domains, but you can add new synonym values that arepresented to the user.

Deleting synonyms of internal valuesYou can delete a synonym of an internal value when it is no longer useful.

About this task

In synonym domains, you can delete synonym values, with the followingconditions:v You can delete only non-default synonym values.v If you delete one synonym value for which you have specified an organization

or site, you must delete all other values for which you have specified thatorganization or site.

v Do not delete synonym values if you have records referencing them.

Procedure1. Open the Domains application.2. In the Domains table window, find the domain with the synonym value that

you want to delete and click Edit Detail.3. In the SYNONYM Domain table window, click the Mark Row for Delete icon.

You can mark multiple rows.To cancel a deletion, click the Undo Delete icon.

4. Click OK.Parent topic: “Working with domains as the configuration administrator” on page19Related concepts:“Synonym domains” on page 18Synonym domains are special domains that are reserved by the system. You cannotadd new synonym domains, but you can add new synonym values that arepresented to the user.

Deleting domainsYou can delete most domains when they are no longer useful.

About this task

You cannot delete a synonym domain.

You can delete other types of domains, but not if the domain is assigned to anattribute. To delete the domain, you must first disassociate the attribute.

Deleting a domain does not affect values that have already been inserted onrecords. For example, if a user inserts a value in a field using a domain selectvalue list, that value remains on the record. The record remains on the record evenif the domain is later disassociated from the attribute and deleted.


Procedure1. Open the Domains application.2. In the Domains table window, find the domain that you want to delete and

click the Mark Row for Delete icon.3. In the warning message, click Yes.4. Optional: You can click the Undo Delete icon to cancel the deletion.5. Click Save Domain.Parent topic: “Working with domains as the configuration administrator” on page19

Working with domains as the system provider or as a tenantuser

You use domains to choose values associated with specific fields. The lists ofdefined values are known as domains (sometimes referred to as value lists). Thesystem uses many domains in its applications. The default domain values are setby the configuration administrator. As a the multitenancy system provider or as atenant user, you can add and remove values and rules in domains to meet thebusiness needs of your organization.

“Adding alphanumeric domains”As the system provider or as a tenant user, you add an alphanumeric (ALN)domain when you want to add a domain that uses one of the alphanumericdata types.“Associating domain values with conditions” on page 41As the system provider or as a tenant user, you can associate domain valueswith a condition to limit the number of values available to users for certainconditions such as statuses, priorities, and assets. This association ensures thatonly users determined by you can set certain statuses, change the priority ofwork orders, and so on.“Creating synonyms of internal values” on page 41As the system provider or as a tenant user, you can create synonyms of internalvalues so that you can present different values to users based on your businessneeds.“Deleting synonyms of internal values” on page 43As the system provider or as a tenant user, you can delete a synonym of aninternal value when it is no longer useful.“Deleting domains” on page 43As the system provider or as a tenant user, you can delete most domains whenthey are no longer useful.

Parent topic: “Domains in a multitenancy system” on page 13

Adding alphanumeric domainsAs the system provider or as a tenant user, you add an alphanumeric (ALN)domain when you want to add a domain that uses one of the alphanumeric datatypes.

About this task

Because you can use a domain with multiple fields, the length you specify must beless than or equal to the length of the shortest field with which you intend to usethe domain. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less. If you specify a length greaterthan the field the domain is used in, you cannot assign the domain to the attributein the Database Information application. Alternatively, you can specify a greater


length in the Domains application and use the Database Information application tochange the length of the field that uses the domain.

Procedure1. Open the Domains application.2. At the bottom of the Domains table window, click Add New Domain and

select Add New ALN Domain.

3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. In the Length field, specify a length that is equal to or less than the length of

the field that uses the domain. For example, if you are adding a domain for afield in the Assets application that has a length of 12, then specify a length of12.

7. Click New Row.8. Fill the Value and Description fields.9. Optional: Apply a domain value to a specific organization or site by entering

the relevant values in the Organization and Site fields. Domains are appliedat the system level by default.You can leave the Organization and/or Site fields empty for all values so thatusers in all organizations and sites can access them. Or you could specify anorganization and/or site for all values so that only the users in the specifiedorganizations and/or sites can access them. Otherwise, complicated outcomescan result.For example, if you enter a value RED with no organization specified, a valueGREEN with Organization A specified, and a value BLUE with Organization Bspecified, then records in Organization A has access to GREEN only. Recordsthat are in Organization B has access to BLUE only. Records that are in otherorganizations has access to RED only. When you specify an organizationand/or site for one value, records in that organization and/or site no longerhave access to values that have no organization or site specified.


What to do next


In the Classifications application, you associate a domain with an attribute in theAttributes table window. No further configuration is needed.

If you use a domain in any other context, adding a domain requires additionaltasks:v Associate the new domain with an attribute in the Database Information

application.v Configure the database in the Database Information application.v Use the Application Designer application to modify the user interface as needed.



“Adding crossover domains”As the system provider or as a tenant user, you add a crossover domain whenyou want to add a domain that returns a value from a field in one applicationto a field in another application.“Adding numeric domains” on page 36As the system provider or as a tenant user, you add a numeric domain whenyou want to add a domain that uses one of the numeric data types.“Adding numeric range domains” on page 37As the system provider or as a tenant user, you add a numeric range domainwhen you want to add a domain that uses one of the numeric data types.However, you specify a range rather than specific values.“Adding table domains” on page 39As the system provider or as a tenant user, you add a table domain when youwant to add a domain that draws its values directly from a column in thedatabase. This process creates a dynamic value list because the values it drawsfrom the database might change.

Parent topic: “Working with domains as the system provider or as a tenant user”on page 32

Adding crossover domains:

As the system provider or as a tenant user, you add a crossover domain when youwant to add a domain that returns a value from a field in one application to a fieldin another application.

About this task

Ensure that the SQL statements that you use in this procedure are valid. Theapplication does not validate SQL statements.

Procedure

1. Open the Domains application.2. In the Domains table window, click Add New Domain and select Add New

CROSSOVER Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Crossover Domain table window, click New Row.6. Define details for the crossover domain:

Field Description

Object Select the name of the object that containsthe attribute that you want to create adomain from. For example, to obtain valuesfrom the ASSET object, select ASSET.


Field Description

Validation Where Clause If the value to be validated by this domainis considered valid, type the part of theclause that when queried against the objectin the Object field returns at least onerecord.

For example, if you want a field named Z(attribute Z) to contain values from theassetnum field in the Assets application, youwould type: ASSETNUM = :Z (the colonrepresents the bind variable).

List Where Clause Type the part of the clause that specifies thevalue that you want to select based on thevalidation WHERE clause.

For example, to select asset records thatbegin with the numbers 114, type ASSETNUMLIKE '114%'

7. Optional: Specify a group value and a key value to select an error message todisplay when domain validation fails. You define values for error messages inthe Database Information application.a. In the Error Message Group field, specify the group value of the error


8. Optional: To apply a domain to a specific organization or site, specify valuesin the Organization and Site fields. To allow access to users in allorganizations and sites, clear all values from these fields.

9. Select fields for the crossover domain:a. In the Crossover Fields table window, click New Row.b. In the Source Field list, select an attribute of the object that you specified

in the Object field. This attribute represents the field from which you wantto return values.

c. In the Destination Field text box, specify the field to which you wantvalues to be returned.

d. Optional: Select the Accept NULL Value check box to copy the value fromthe source field when the value of the target attribute is empty. Thisfunction overwrites the previous value.

e. Optional: Select the No Overwrite check box if you want to copy the valueof the source attribute when it is null.

10. Optional: Specify conditions for the source object or the destination object, orboth:a. In the Condition on Source field, select a condition or use the Conditional

Expression Manager to build the condition for the source object of thecrossover. The source object must meet the condition before the crossoveroccurs.

b. In the Condition on Destination field, select a condition or use theConditional Expression Manager to build the condition for the destinationobject of the crossover. The destination object must meet the conditionbefore the crossover occurs.


c. In the Sequence field, type a numeric value to specify the order that thecrossover occurs when multiple crossovers are defined. Crossovers withlower values occur before crossovers with higher values.

11. Click OK to add the crossover domain to the database.

What to do next






Parent topic: “Adding alphanumeric domains” on page 32

Adding numeric domains:

As the system provider or as a tenant user, you add a numeric domain when youwant to add a domain that uses one of the numeric data types.

About this task

Because you can use a domain with multiple fields, the length that you specifyhere must be less than or equal to the length of the shortest field with which youuse the domain. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less for the domain. If you specify alength greater than the field the domain is used in, you are not able to assign thedomain to the attribute in the Database Information application. Alternatively, youcan specify a greater length in the Domains application. You can use the DatabaseInformation application later to change the length of the field that uses thedomain.

Procedure


select Add New NUMERIC Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. Depending on the data type the Length field might or might not be editable.



7. For Decimal data type only, in the Scale field, specify a scale value if differentfrom the default, 2.

8. Click New Row.9. Fill the Value and Description fields.

10. Optional: Apply a domain value to a specific organization or site byspecifying values in the Organization and Site fields. Domains are applied atthe system level by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify an organization and/or site for all values so that only users inthe specified organizations and/or sites can access them. Otherwise,complicated outcomes can result.For example, if you enter a value 100 with no organization specified, a value300 with Organization A specified, and a value 500 with Organization Bspecified, then records in Organization A have access to 300 only. Records thatare in Organization B have access to 500 only. Records that are in otherorganizations have access to 100 only. Once you specify an organizationand/or site for one value, records in that organization and/or site no longerhas access to values that have no organization/site specified.


What to do next







Adding numeric range domains:

As the system provider or as a tenant user, you add a numeric range domain whenyou want to add a domain that uses one of the numeric data types. However, youspecify a range rather than specific values.

About this task

Because you can use a domain with multiple fields, the length that you specifyhere must be less than or equal to the length of the shortest field you use thedomain with. For example, if you want to use the domain with three fields oflengths 8, 10, and 12, specify a length of 8 or less for the domain. If you specify alength greater than the field the domain is used in, you cannot assign the domain


to the attribute in the Database Information application. Alternatively, you canspecify a greater length in the Domains application. You can use the DatabaseInformation application later to change the length of the field that uses thedomain.

Procedure


select Add New NUMERIC RANGE Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. In the Data Type field, specify a data type for the domain.6. Depending on the data type, the Length field might or might not be editable.


7. For DECIMAL data type only, in the Scale field, specify a scale value ifdifferent from the default, 2.

8. Click New Row and fill the following fields. Each row defines a range.

Field Description

Range Segment Specify an identifying number for thesegment. For example, 1 if the range has justone segment, or 1, 2, or 3 if the domain hasthree segments.

For a range with regular intervals or asimple continuous range, you need only onesegment.

Range Minimum Specify the lowest value in the range, forexample, 10 in the range 10 to 50.

You can leave either the Range Minimumfield or the Range Maximum field empty(null value), but not both.

Range Maximum Specify the highest value in the range, forexample, 50 in the range 10 to 50.

You can leave either the Range Minimumfield or the Range Maximum empty (nullvalue), but not both.

Interval For a range with discrete values, specify thevalue of the interval that separates thevalues you want to appear in the list. Forexample, the interval is 10 in the range 10 -50 if you want the values 10, 20, 30, 40, and50 to be valid.

For a continuous range of values betweenthe minimum and maximum values, leavethis field null (empty).

Continuous is relative to the data type. Forexample, if the data type is INTEGER andthe range is 1 - 5, then only 1, 2, 3, 4, and 5are valid values.


9. Optional: Apply a domain value to a specific organization or site byspecifying values in the Organization and Site fields. Domains are applied atthe system level by default.You might want to leave the Organization and/or Site fields empty for allrange segments so that users in all organizations and sites can access them. Oryou could specify an organization and/or site for all range segments so thatonly users in the specified organizations and/or sites can access them.

10. Optional: Click New Row again to add ranges for additional segments.11. Click OK.

What to do next







Adding table domains:

As the system provider or as a tenant user, you add a table domain when youwant to add a domain that draws its values directly from a column in thedatabase. This process creates a dynamic value list because the values it drawsfrom the database might change.

Procedure


select Add New TABLE Domain.3. In the Domain field, specify a name for the domain.4. In the Description field, type a short description for the domain.5. Click New Row and fill the following fields.

Field Description

Object Specify the name of the object. The objectyou want is the object containing theattribute from which you want to create adomain.

For example, to obtain values from theASSET object, specify ASSET.


Field Description

List Where Clause Type the part of the clause that specifies thevalues that you want to select based on thevalidation WHERE clause.

For example, to select asset records thatbegin with the numbers 114, type: assetnumlike '114%'

Attention: The system does not validateyour entry for syntax or any other errors. Besure that you have typed a correct WHEREclause. If you make errors, errors do notbecome apparent until you configure thedatabase.

Validation Where Clause If the value to be validated by this domainis considered valid, type the part of theclause that when queried against the objectin the Object field should return at least onerecord.

Usually, the clause involves a bind variablefor the field that uses this domain forvalidation. The bind variable is representedby a colon (:) followed by the field name.

For example, if you want a field named Z(attribute Z) to contain values from theassetnum field in the Assets application,type: assetnum = :z

6. Optional: Specify a group value and a key value to select an error message todisplay when domain validation fails. You define values for error messages inthe Database Information application.a. In the Error Message Group field, specify the group value of the error


7. Optional: Apply a domain value to a specific organization or site by specifyingvalues in the Organization and Site fields. Domains are applied at the systemlevel by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify organization and/or site for all values so that only users in thespecified organizations and/or sites can access them.

8. Optional: Click New Row again to add more rows.9. Click OK.

What to do next








Associating domain values with conditionsAs the system provider or as a tenant user, you can associate domain values with acondition to limit the number of values available to users for certain conditionssuch as statuses, priorities, and assets. This association ensures that only usersdetermined by you can set certain statuses, change the priority of work orders, andso on.

Before you begin

Before you associate a domain value with a condition, you must set up the domainvalues for the ALN, synonym, and numeric domains. You must then define acondition for when particular domain values should appear in a domain.

About this task

You can create a condition in the condition library of the Conditional ExpressionManager application. If you modify the condition for a domain value after thevalue has been selected for a field, the existing values are not revalidated. There isno current record on the Search or List pages so conditional values are notsupported on these pages.

Procedure1. Open the Domains application and select the Edit Detail icon for the domain

containing the values you want to associate with a condition. Depending on thedomain type selected, an ALN, numeric, synonym, table, or crossover windowopens from where you can add or change conditions.

2. Add or change the conditions as necessary.3. Optional: If you want to add the same conditions for multiple domain values,

select Set Conditions and select a condition from the condition library. You canapply the same condition to all of the selected values.

4. Optional: If you want domain values to be used by multiple objects, specify theobjects in the Object Name field.

5. Save the record.Parent topic: “Working with domains as the system provider or as a tenant user”on page 32

Creating synonyms of internal valuesAs the system provider or as a tenant user, you can create synonyms of internalvalues so that you can present different values to users based on your businessneeds.

Procedure1. Open the Domains application.


2. Find the synonym domain for which you want to add a synonym value, forexample WOSTATUS.

3. Click Edit Detail. In the Synonym Domain table window, the set of currentvalues: the Internal Value is used by the system and must be unique. The Valueand its description are what users see.

4. Click New Row and enter values in the fields:

Field Description

Internal Value Specify the internal value for which youwant a synonym.

For example, in the WOSTATUS domain, ifyou want to create a synonym for WAPPRcalled WAIT, you would specify the WAPPRinternal value.

Value Specify the synonym value you want a userto see.

For example, WAIT.

Description Type a description of the synonym todifferentiate it from the existing value.

5. Optional: In the Default field, select the check box if you want the system touse the new synonym value by default. Each internal value can have only onedefault synonym value.For example, the system inserts WAPPR (Waiting for Approval) as the statuswhen you create a work order. You add a synonym value, WAIT. If you wantthe system to insert WAIT instead of WAPPR, then make WAIT the default.

6. Optional: Apply a domain value to a specific organization or site by specifyingvalues in the Organization and Site fields. Domains are applied at the systemlevel by default.You might want to leave the Organization and/or Site fields empty for allvalues so that users in all organizations and sites can access them. Or youcould specify organization and/or site for all values so that only users in thespecified organizations and/or sites can access them.If you create a synonym value and specify a site or organization, and then clickOK, the system automatically inserts duplicate rows for the other values. Theduplicate rows have the site or organization you specified for the new valuethat you created. For example, the MRTYPE domain has three values:RECURRING, STANDARD, and TRANSFER (each with an internal value of thesame name). If you create a synonym value, REGULAR, with the internal valueof STANDARD and specify Organization B, the system automatically creates(when you click OK) the additional synonym values RECURRING andTRANSFER with Organization B specified.

Important: After you have implemented the system and inserted records, yougenerally must not add a synonym value with a site or organization specified.This action can invalidate existing data. If you must add a synonym value witha site or organization specified, you must also add synonym values for all theexisting values that are in the database. For example, if you added a synonymvalue for STANDARD with an organization or site specified, you must also addsynonym values for RECURRING and TRANSFER (if they have been used onrecords) with the same organization or site specified.

7. Click New Row to add more synonyms.


8. Click OK.Parent topic: “Working with domains as the system provider or as a tenant user”on page 32

Deleting synonyms of internal valuesAs the system provider or as a tenant user, you can delete a synonym of aninternal value when it is no longer useful.

About this task

In synonym domains, you can delete synonym values, with the followingconditions:v You can delete only non-default synonym values.v If you delete one synonym value for which you have specified an organization

or site, you must delete all other values for which you have specified thatorganization or site.

v Do not delete synonym values if you have records referencing them.

Procedure1. Open the Domains application.2. In the Domains table window, find the domain with the synonym value that

you want to delete and click Edit Detail.3. In the SYNONYM Domain table window, click the Mark Row for Delete icon.

You can mark multiple rows.To cancel a deletion, click the Undo Delete icon.

4. Click OK.Parent topic: “Working with domains as the system provider or as a tenant user”on page 32

Deleting domainsAs the system provider or as a tenant user, you can delete most domains whenthey are no longer useful.

About this task

You cannot delete a synonym domain.

You can delete other types of domains, but not if the domain is assigned to anattribute. To delete the domain, you must first disassociate the attribute.

Deleting a domain does not affect values that have already been inserted onrecords. For example, if a user inserts a value in a field using a domain selectvalue list, that value remains on the record. The record remains on the record evenif the domain is later disassociated from the attribute and deleted.

Procedure1. Open the Domains application.2. In the Domains table window, find the domain that you want to delete and

click the Mark Row for Delete icon.3. In the warning message, click Yes.4. Optional: You can click the Undo Delete icon to cancel the deletion.5. Click Save Domain.


Parent topic: “Working with domains as the system provider or as a tenant user”on page 32

Crontasks in a multitenancy systemTenants can run their own instances of crontasks. If one tenant runs a crontask onone schedule and a second tenant runs the same crontask on a different schedule,the crontasks will run independently and will not impact each other.

The system provider can add a property that will force the crontasks for aparticular tenant to run on a particular server.

Cron task setup overviewCron tasks are behind-the-scene jobs that run automatically and on a fixedschedule. You can use the default cron tasks. You can also create your own crontasks. Cron tasks include activities such as generating preventive maintenancework orders and reordering inventory items on schedules.


Reports in a multitenancy systemAs the system provider you can administer and run predefined reports. You canalso import new and updated reports to the multitenancy system. As a tenant useryou can run the set of reports delivered by the system provider.

Tenants cannot import new reports. Tenants cannot add report definitions, but theycan customize reports to support their business needs.

When a report is reimported by the system provider, for example, when a bug fixversion is delivered, a notification is sent to all tenants that informs them that anew version of the report is available. Then, each tenant can review the reportchange. Tenants can choose to use the report as is or individual tenants cancustomize the report to suit their business needs. If a tenant customized a previousversion of the report, the tenant can merge the new version of the report with thecustomized version of the report.Parent topic: Chapter 3, “Administering a multitenancy system,” on page 9Related information:

Reports information on the IBM Maximo Asset Management wiki

Bulletin boards in a multitenancy systemIn a multitenancy system, tenant users can create bulletin board messages. Theycan specify the audience for the messages from within users of the same tenant. Inaddition, the system provider can use the bulletin board to broadcast messages toall tenants.

In a multitenancy system, a tenant user with access to the bulletin board can use itto communicate with other users of the same tenant.

In addition, the system provider can use the bulletin board to broadcast messagesto all tenants. Broadcast messages from the system provider are displayed on thebulletin board of all tenant users.

Managing bulletin boardsYou use bulletin boards to post messages about critical problems and incidents,and to broadcast information throughout an organization. You can also view


http://www.ibm.com/developerworks/wikis/display/maximo/Reports

communication logs from service desk agents and their users, andcommunications that are generated by workflow processes and escalations.



Chapter 4. Managing tenants

As the multitenancy system provider, you can add, activate, and disable tenantrecords. You can also modify tenant details in existing records.

“Adding tenants”You can add tenants to your multi-tenant system by entering a tenant code andsome general information about the tenant. You also add an administrative userand a database user for the tenant. When you create a tenant record, an email issent to the tenant that contains the tenant administrator password.“Activating and disabling tenant accounts” on page 48The multitenancy system provider can activate and deactivate tenant accounts.If a tenant account is disabled, then none of the users that are associated withthat tenant code can access the system.“Modifying tenants” on page 48The multitenancy system provider can reset passwords. The multitenancysystem provider can also modify their own general information and the generalinformation of tenants. It is not possible to modify the tenant code, the tenantadmin login ID, or the tenant database user name.“Adding tenant users” on page 48You can add users to the multitenancy system. Each user is associated with onetenant code. The user name must be unique within the associated tenant code.“Communicating with tenants using the bulletin board” on page 49The system provider can communicate with all tenants by broadcasting amessage on the bulletin board.

Adding tenantsYou can add tenants to your multi-tenant system by entering a tenant code andsome general information about the tenant. You also add an administrative userand a database user for the tenant. When you create a tenant record, an email issent to the tenant that contains the tenant administrator password.

Procedure1. In the Tenants application, click New Tenant.2. On the Tenant tab, enter the tenant details, including the tenant code, the

tenant admin login ID, and the tenant database user ID. The tenant code, andthe tenant database user name must be unique for each tenant you create.

3. Save the record.4. Optional: To send the tenant an email that contains the tenant admin login ID

and the tenant code, select Select Action > Send Login Information.

Resultsv A tenant record is created. After saving, the tenant admin login ID and the

tenant database user ID cannot be modified.v An area of the database is isolated for the tenant’s data. The database area is

populated with template data and delta storage data. The tenant-level systemproperties are added to the database.

v An email is sent to the tenant’s contact email address. The email contains anauto-generated password. The user must change this password after it is firstused.


v If you selected Send Login Information, then a second email is sent to theprimary email contact address of the tenant. This email contains the tenantadmin login ID and the tenant code.

What to do next

You can now add users for this tenant.Parent topic: Chapter 4, “Managing tenants,” on page 47Related concepts:“Tenants” on page 3Client organizations that sign up to use a multitenancy system are called tenants.Tenants are added to the multitenancy system by the multitenancy systemprovider. Every tenant is associated with a tenant identifier (tenant ID). Users ofthe multitenancy system are generally employees of the client organization.

Activating and disabling tenant accountsThe multitenancy system provider can activate and deactivate tenant accounts. If atenant account is disabled, then none of the users that are associated with thattenant code can access the system.

Procedure

Using the multitenancy system provider credentials, log on to the multitenancysystem. In the Tenants application, select the tenant you want to activate ordisable.1. Activate the tenant by changing the tenant status to active. Users who are

associated with the specified tenant code selected can access the system.2. Disable the tenant by changing the tenant status to inactive. Users who are

associated with the specified tenant code selected cannot access the system.

When you change the status of a tenant record, the record is auto-saved.Parent topic: Chapter 4, “Managing tenants,” on page 47

Modifying tenantsThe multitenancy system provider can reset passwords. The multitenancy systemprovider can also modify their own general information and the generalinformation of tenants. It is not possible to modify the tenant code, the tenantadmin login ID, or the tenant database user name.

Procedure1. In the Tenants application, select the tenant that you want to modify.2. Optional: To reset the tenant password, select Reset Password from the Select

Action menu. An email containing the new password is sent to the tenant. Thispassword expires when it is first used.

3. Optional: Modify the tenant’s general details and save the record.Parent topic: Chapter 4, “Managing tenants,” on page 47

Adding tenant usersYou can add users to the multitenancy system. Each user is associated with onetenant code. The user name must be unique within the associated tenant code.


Before you begin

A user record must have a corresponding person record. You create person recordseither in the People application or in the Personal section in the Users application

Procedure1. Access the system using your tenant administrator credentials.2. In the Users application, click Add user.3. Enter a user name. Tenants can use their email address as their user name. If

the email address is too long for the user name, then the email address isshortened to meet the user name requirements. You can change this shortenedemail address to another value.

4. Enter the user details5. Save the record.Parent topic: Chapter 4, “Managing tenants,” on page 47Related concepts:“Tenants” on page 3Client organizations that sign up to use a multitenancy system are called tenants.Tenants are added to the multitenancy system by the multitenancy systemprovider. Every tenant is associated with a tenant identifier (tenant ID). Users ofthe multitenancy system are generally employees of the client organization.

Communicating with tenants using the bulletin boardThe system provider can communicate with all tenants by broadcasting a messageon the bulletin board.Parent topic: Chapter 4, “Managing tenants,” on page 47

Chapter 4. Managing tenants 49

Chapter 5. Modules and applications

You can access multi-tenant applications from the Go To menu in the Navigationtoolbar of the user interface.

“Database Information application”Tenant users can view and download database information in the DatabaseInformation application.

Database Information applicationTenant users can view and download database information in the DatabaseInformation application.

In the Database Information application, you can view information about databaseobjects and attributes, for example, field lengths, and attribute names. You can alsoview the actions that are available for electronic signature on the system. Thesystem provider and tenant users can modify attributes, however there are rulesgoverning how the attributes can be changed.

You can download information from any table window.

The information that is shown in the Database Information application is aread-only subset of the database information in the Database ConfigurationApplication. Only the configuration administrator can modify database propertiesin the Database Configuration application.

“Adding an attribute to an application”As a tenant, you can add an attribute to an application from pre-defined extratables. These tables are used to store additional data but there are limits on howthe data can be entered.“Rules for modifying attributes” on page 52There are limits on how the system provider and tenants can modify attributesusing the Database Information application.“Defining a lookup map” on page 53As a tenant, you can define a lookup map to associate a source object and asource field with a target object and related fields. The product ships withmany lookup maps, but you can define your own lookup maps for objects thatyou create.“Adding system messages” on page 53As a tenant administrator, you can add and change the system messages thatdisplay when required to assist users as they use the application. To work withthe system messages you must have the signature option Messages assigned toyour user group.

Parent topic: Chapter 5, “Modules and applications”

Adding an attribute to an applicationAs a tenant, you can add an attribute to an application from pre-defined extratables. These tables are used to store additional data but there are limits on howthe data can be entered.


Procedure1. In the Database Information application, select the attribute or attributes that

you want to modify.2. Enter the modifications. There are rules that govern the modifications that you

can make.3. Save your changes. The modified attributes have the status Change.4. From the Select Action menu, select Apply Changes.5. Optional: If you want to cancel the modifications and revert to the original

values of the attributes, from the Select Action menu, select Discard Changes.

Results

The modified attribute value is available to the Tenant that modified the value.Parent topic: “Database Information application” on page 51Related concepts:“Rules for modifying attributes”There are limits on how the system provider and tenants can modify attributesusing the Database Information application.

Rules for modifying attributesThere are limits on how the system provider and tenants can modify attributesusing the Database Information application.

Table 7. Rules for modifying attributes

Field Editable Rules for editing

Attribute No Not applicable.

Title Yes None.

Description Yes None

Domain Yes v Users can add a domain to a field that does not have adomain or a field validation class.

v Users can modify a domain that they have added.

Type Yes v The Type UPPER can be changed to to ALN.

v The Type LOWER can be changed to ALN.

v The Type DATE can be changed to DATETIME.

v The Type AMOUNT can be changed to DECIMAL.

v The Type DURATION can be changed to FLOAT.

Default value Yes None

Length Yes Users can

Scale No Not applicable.

Required? Yes v Users can change the value from 0 to 1.

v If the tenant has set the value to 1, and the master value is 0,then the tenant can set the value to 0.

Persistent? No Not applicable.

Audit enabled? Yes v Users can change the value from 0 to 1.



Table 7. Rules for modifying attributes (continued)

Field Editable Rules for editing

E-signatureEnabled?

Yes v Users can change the value from 0 to 1.


MultilanguageSupported?

No Not applicable

Multilanguagein Use?

No Not applicable

Parent topic: “Database Information application” on page 51Related tasks:“Adding an attribute to an application” on page 51As a tenant, you can add an attribute to an application from pre-defined extratables. These tables are used to store additional data but there are limits on howthe data can be entered.

Defining a lookup mapAs a tenant, you can define a lookup map to associate a source object and a sourcefield with a target object and related fields. The product ships with many lookupmaps, but you can define your own lookup maps for objects that you create.

Procedure1. On the Attributes tab of the Database Information application, select the

attribute for which you want to specify details.2. Click Edit Lookup Map.3. Click New Row.4. Specify the following details for the target attribute:

v In the Target Attribute field, select the attribute to which you want to returnvalues.

v In the Source Object field, specify the source from which values arereturned.

v In the Source Key field, specify the key of the source object from which youwant to return values.

v In the Sequence field, specify a numeric value to determine the attributesthat are to be set before other attributes. A lower numeric value has priorityover a higher numeric value.

5. Optional: Select the Allow Null check box if you want the target attribute toaccept null values.

6. Click OK.Parent topic: “Database Information application” on page 51

Adding system messagesAs a tenant administrator, you can add and change the system messages thatdisplay when required to assist users as they use the application. To work with thesystem messages you must have the signature option Messages assigned to youruser group.

Chapter 5. Modules and applications 53

Before you begin

Ensure that your user group has the signature option Messages assigned to it.

Procedure1. In the Database Information application, from the Select Action menu, select

Messages.2. Click New Row and specify the message group to which you want the new

message to belong.3. In the Message Key field, type a unique string that you want to be associated

with the message.4. Specify the display method for the message.5. In the Message ID field, specify the prefix and product to be associated with

the message. Customer-generated messages typically use the BMXZZ prefix.The complete identifier is generated when you click the prefix.

6. Select the Display ID check box to display the message identifier whenever themessage is displayed.

7. In the Value field, enter the message text.8. In the Buttons, and Explanation and Responses sections, specify additional

details.9. Click New Row to add more messages, or click OK to save your changes.Parent topic: “Database Information application” on page 51


Chapter 6. Multitenancy reference

Supplementary information is available to describe multitenancy features.“Template data tables”Tables that are copied and added to the database when a tenant is created.“Master data tables” on page 57Specific tables that contain data that is shared by all tenants. Tenants can adddata to these tables. This additional data is flagged with the tenant ID for thattenant, and is stored as delta data.“Multitenancy system properties” on page 59The configuration administrator sets the system level properties that are used astemplate data for the tenants. The Configuration administrator can modify allsystem properties. The system provider and tenant users can modify a limitednumber of system properties to tailor the system to support their needs.

Template data tablesTables that are copied and added to the database when a tenant is created.v ACTIONGROUPv APPDOCTYPEv APPLICATIONAUTHv AUTOKEYv COMMTEMPLATEv COMMTMPLTSENDTOv CONTRACTDEFAULTv CONTRACTPROPERTYv COSTTYPEv CRONTASKINSTANCEv CRONTASKPARAMv CTRLCONDITIONv CTRLCONDPROPv CTRLGROUPv DEFAULTQUERYv DMPACKAGEDEFv DMPKGCFGGRPDEFv DMPKGDEFSTATUSv DOCTYPESv ESCALATIONv ESCNOTIFICATIONv ESCREFPOINTv FSNOBJPROPERTYv FSNREFPROPERTYv FSNSQLCOLUMNv FSNSQLTABLEv L_COMMTEMPLATE


v L_COSTTYPEv L_CTRLCONDPROPv L_KPIMAINv L_QUERYv L_SKDACTIONv L_SKDDATAGROUPv L_SKDPROPERTYv L_SKDRESOURCEVIEWv MAPTIPDEFAULTSv GROUPUSERv GRPREASSIGNAUTHv KPIMAINv KPITRENDCFGv LONGDESCRIPTIONv MAXENDPOINTv MAXENDPOINTDTLv MAXEXTIFACEINv MAXEXTIFACEOUTv MAXEXTLISTVALv MAXEXTSYSCONTROLv MAXEXTSYSTEMv MAXIFACEINVOKEv MAXIFACEOUTCNTLv MAXINTLISTENERv MAXINTPOLICYv MAXINTPOLICYPARAMv MAXGROUPv MAXLAUNCHENTRYv MAXLECONTEXTv MAXROLEv MAXUSERv PERSONv PERSONANCESTORv PORTLETv QUERYv REPORTv REPORTAPPAUTHv REPORTLABELv REPORTLOOKUPv REPORTOSAUTHv SECURITYRESTRICTv SKDACTIONv SKDDATAGROUPv SKDOBJECTv SKDOBJECTMGR


v SKDPROPERTYv SKDPROPERTYMAPv SKDRESOBJECTv SKDRESOURCEVIEWv TLOAMPRMDFLTv TLOAMSWCATALOGv WFACTIONv WFAPPTOOLBARv WFASSIGNMENTv WFCONDITIONv WFINTERACTIONv WFNODEv WFNOTIFICATIONv WFPROCESSv WFREVISIONv WFSTARTv WFSTOPv WFTASKParent topic: Chapter 6, “Multitenancy reference,” on page 55Related concepts:“The configuration administrator” on page 3The multitenancy system provider administers and maintains the tenant templatedata. The system provider uses the configuration administrator tenant toadminister the initial data that is added to the database when a tenant is created.“Tenant data in a multitenancy database” on page 4When a tenant is created, an area of the database is isolated for the tenant’s data.The database area is populated with system data, template data, and master data.Related tasks:“Configuring template data” on page 6When a tenant record is added to the multitenancy system, an area of the databaseis isolated for the tenant’s data. The database area is populated with template dataand delta storage data. The system provider can configure and modify the initialtemplate data using the configuration administrator tenant.

Master data tablesSpecific tables that contain data that is shared by all tenants. Tenants can add datato these tables. This additional data is flagged with the tenant ID for that tenant,and is stored as delta data.v ACTIONv ALNDOMAINv CONDITIONv CROSSOVERDOMAINv CRONTASKDEFv DMCFGGROUPv DMCFGOBJECTv DMCOLLLOOKUPRULEv DMCOLLPKGEXCEPTION

Chapter 6. Multitenancy reference 57

v DMCOLLRELRULEv DMCOLLRELRULECOLSv DMDEPENDENCYv LANGUAGEv MAXAPPSv MAXATTRIBUTEv MAXATTRIBUTECFGv MAXCONDDETAILv MAXCONTROLVALUEv MAXDOMAINLINKv MAXDYNAMICDOMLINKv MAXINTOBJECTv MAXINTOBJDETAILv MAXINTOBJCOLSv MAXINTOBJALIASv MAXIFACEINv MAXIFACEOUTv MAXHANDLERv MAXIFACEPROCv MAXIFACECONDv MAXIFACECONTROLv MAXPROCCOLSv MAXREPLACEPROCv MAXTRANSFORMPROCv MAXDOMAINv MAXLABELSv MAXLOOKUPMAPv MAXMENUv MAXMESSAGESv MAXMODULESv MAXOBJECTv MAXOBJECTCFGv MAXPRESENTATIONv MAXPROPv MAXPROPVALUEv MAXRELATIONSHIPv MAXSYSINDEXESv MAXSYSKEYSv MAXTABLEv MAXTABLECFGv MAXTABLEDOMAINv MAXVARSv MAXVARTYPEv MAXVIEWv MAXVIEWCFG


v MAXVIEWCOLUMNv MAXVIEWCOLUMNCFGv MAXSERVSECURITYv MXCOLLABv MXCOLLABREFv NUMERICDOMAINv NUMRANGEDOMAINv PALETTEITEMv PROPERTYASSOCv RESULTSETCOLSv SIGOPTFLAGv SIGOPTIONv SYNONYMDOMAIN

Parent topic: Chapter 6, “Multitenancy reference,” on page 55Related concepts:“The configuration administrator” on page 3The multitenancy system provider administers and maintains the tenant templatedata. The system provider uses the configuration administrator tenant toadminister the initial data that is added to the database when a tenant is created.“Tenant data in a multitenancy database” on page 4When a tenant is created, an area of the database is isolated for the tenant’s data.The database area is populated with system data, template data, and master data.Related tasks:“Configuring template data” on page 6When a tenant record is added to the multitenancy system, an area of the databaseis isolated for the tenant’s data. The database area is populated with template dataand delta storage data. The system provider can configure and modify the initialtemplate data using the configuration administrator tenant.

Multitenancy system propertiesThe configuration administrator sets the system level properties that are used astemplate data for the tenants. The Configuration administrator can modify allsystem properties. The system provider and tenant users can modify a limitednumber of system properties to tailor the system to support their needs.

“Asset properties” on page 62You can use system properties to help manage assets.“Attached document properties” on page 62You can specify property values to control the use of attachments across thesystem.“Automation scripts properties” on page 66You can use system properties to help manage automation scripts.“Bidirectional language properties” on page 66You can use system properties to enable and manage bidirectional languagesupport.“Bulletin board property” on page 67You can use the property to track viewed and unviewed messages in thebulletin boards.


“Calendar property” on page 67You can use the property to specify the system base calendar.“Classification item properties” on page 67You can use classification items (CI) properties to specify data set providerclasses for CI and actual CI.“Communication template property” on page 67You can use the property to specify whether bind variables are ignored in thecommunication templates.“Condition property” on page 67You can use the property to list comma-separated table names that are excludedwhen the reference for a condition is checked.“Cron task properties” on page 68You can use properties to manage cron tasks.“Database properties” on page 68You can use system properties to help manage the database.“Deployed assets property” on page 74You can use the property to specify the data set provider class for deployedassets.“Email interaction properties” on page 74With email interaction, users without access to a desktop can change objectsand workflow assignments. Email interaction adds system properties and eachproperty must have a unique value.“Email listener properties” on page 76You can use system properties to help manage email listener properties.“Environment properties” on page 76You can use system properties to help manage the system environment.“E-signature properties” on page 77Electronic signatures confirm that a person who modifies a record is the sameperson that logged in to the system. You can use the properties to manage thee-signature feature for your organization.“General ledger property” on page 78You can use the property to control the use of the upper function for the GLaccount in QBE.“Inventory property” on page 78You can use the property to set the maximum inventory usage line limit in aninventory usage document.“Issues and transfers property” on page 78You can use the property to open the Long Operation window when anINVISSUE is saved and the processing time is long.“Lightweight Directory Access Protocol integration properties” on page 78You can use system properties to manage Lightweight Directory AccessProtocol (LDAP) integration.“maximo.properties file” on page 79You must define system properties in the maximo.properties file to ensure thatthe application server starts. If you do not define these properties, an errormessage is written to the log file of the system or to the application serverconsole.“Migration Manager properties” on page 80You use Migration Manager to migrate configuration content from one productenvironment to another. You can use the properties to control the migration ofthe configuration content.


“mxe.help properties” on page 82The mxe.help system properties connect the user interface to the informationcenter. Some of the properties are used to construct the link that opens theinformation center. To ensure that information center is available, match thevalues in the mxe.help properties to the information center that you deploy.“OSLC properties” on page 83You can use system properties to help manage Open Services for LifecycleCollaboration (OSLC) application integration.“Reorder property” on page 84You can use the reorder property to manage the reorder time out periods foryour organization.“Report integration properties” on page 84You can use report properties to control how reports are created and managed.You can identify all the report properties if you specify report as a filter valuein the Description field.“Security properties” on page 88The data types Crypto and CryptoX are used to encrypt passwords and othertypes of confidential information. You use security properties to specify securitylevels for your organization, such as the data that must be encrypted and canbe decrypted.“Server properties” on page 91You can use the server properties to control how a server operates, such asspecifying values for the administration user, for user registration, and emailauthentication.“Utilities for logging and testing” on page 95To help you manage system performance, there are utilities that you can use fortesting and debugging purposes. When you are satisfied with your deployment,you can disable these logging utilities.“Work order generation property” on page 96You can use to use a property to manage the generation of work orders.


Parent topic: Chapter 6, “Multitenancy reference,” on page 55Related concepts:“System properties in a multitenancy system” on page 9In a non-multitenancy system, system properties are set at the system level. In amultitenancy system, some properties remain at the system level and are invisibleto tenants. The Configuration Administrator controls the value of these properties.The system provider and tenants can modify a subset of the system properties tosupport their needs. There are rules that govern the ways in which tenants canmodify properties. Tenants can also view some of the properties that they cannotmodify.Related tasks:“Setting multitenancy system properties” on page 12A system property is a key-value pair that is used at the system level. You can setsystem properties that various components use to control how applications andother aspects of the product work. Which properties you can set and modifydepend on your role and is controlled by the ACCESSTYPE of the property. You usethe System Properties application to manage system properties and the values ofthe system properties that various components use.

Asset propertiesYou can use system properties to help manage assets.

Table 8. Asset properties

Property Description Default value

Who canedit thisproperty?

Visibletotenants

Modification restrictionsfor tenants

mxe.app.asset.deleteAttributesAssetMovedBack

Deletes attributes when anasset is moved back to itsoriginal site. The defaultvalue is 0 which is no.

0 Tenants,systemprovider

Yes

mxe.assettopology.depth Represents the maximumdepth that you can go in theasset topology.


Yes The default value canonly be reduced.

mxe.assettopology.init Indicates the initial depth forthe asset topology.



mxe.assettopology.maxnodes

Specifies the maximumnumber of nodes that can beshown in the asset topology.



recon.engine.dataset.map.ASSET

Represents comma-separateddata set names that can bereconciled against assets.

DEPLOYED ASSET Tenants,systemprovider

Yes

recon.engine.dataset.provider.ASSET

Represents the data setprovider class for assets.

psdi.app.recontask.engine.dataset.AssetDataSet

Tenants,systemprovider

Yes

Parent topic: “Multitenancy system properties” on page 59

Attached document propertiesYou can specify property values to control the use of attachments across thesystem.


Table 9. Attached document properties

Property Description Default valueWho can edit thisproperty? Visible to tenants

mxe.doclink.doctypes.allowedFileExtensions

Represents the type offiles that are allowed tobe attached to files onthe application servercomputer.

The application servermust be restarted forthe changes to takeeffect.

pdf, zip, txt, doc,docx, dwg, gif, jpg,csv, xls, xlsx, ppt,xml, xsl, bmp, html

Tenants, systemprovider

Yes

mxe.doclink.doctypes.topLevelPaths

Represents thetop-level doclinksdirectory that stores alldocument folders onthe application servercomputer.

The Default File Pathvalue entered in theManage All DocumentsFolder window mustbe a subdirectory ofthis value.

This value cannot benull.

The application servermust be restarted forthe changes to takeeffect.

The default location is\DOCLINKS, typicallyunder the default driveC:

ConfigurationAdministrator

Yes

mxe.doclink.path1 throughmxe.doclink.path10

Specifies the HTTPserver path to linkdocuments that areattached to records.

This property needs alive refresh only.


Yes

mxe.doclink.doctypes.defpath

Represents the defaultpath for the doclinksfolder on theapplication servercomputer. This folder iswhere the physicaldocuments that areattached to a record arestored.

This value must beconfigured before youcan use the system andneeds a live refreshonly.


Yes


Table 9. Attached document properties (continued)


mxe.doclink.maxfilesize Represents themaximum file size inmegabytes for thedoclinks folder thatcan be uploaded.

You can change thisproperty in the SystemProperties application;however, you mustalso rebuild theEnterprise ApplicationArchive (EAR) file.

10 ConfigurationAdministrator

Yes

mxe.doclink.multilang.aix.websphere

Indicates whether thesystem is running onIBM WebSphereApplication Server onAIX®.

False ConfigurationAdministrator

No

mxe.doclink.multilang.hpux.websphere

Indicates whether thesystem is running onIBM WebSphereApplication Server onHP-UX.


No

mxe.doclink.multilang.linux.websphere

Indicates whether thesystem is running onIBM WebSphereApplication Server onLinux.


No

mxe.doclink.multilang.solaris.websphere

Indicates whether thesystem is running onIBM WebSphereApplication Server onSun Solaris.


No

mxe.doclink.multilang.windows.websphere

Indicates whether thesystem is running onIBM WebSphereApplication Server onMicrosoft Windows.


No

mxe.doclink.defaultPrintDocWithReport

Specifies whetherprintable attachmentsare printed by defaultwhen you print areport.

True Tenants, Systemprovider

Yes

mxe.doclink.autsecuredAttachment

Hides the file path ofdocuments that wereadded by using theAttached Documentsfeature. You can usethis property forsecurity reasons.

The hyperlink for theattachment shows theapplication content rootand the encrypted filename only.

False Tenants, systemprovider

Yes


Table 9. Attached document properties (continued)


mxe.doclink.securedAttachmentDebug

Helps you totroubleshoot when youare using securedattachments to viewthe attachment file.

When security for theattachments is activeand you set the valuefor this property totrue, the attached filename and file pathdisplay in theapplication server log.

False Tenants, systemprovider

Yes

proxy_hostname Indicates the externalhost that enables directprinting.


Yes

proxy_port Indicates the externalport that enables directprinting.


Yes

Doclink path translations

10 properties for doclink path translations are provided. However, theConfiguration Administrator can add properties to the MaxProp table by usingproperty maintenance. The LinkedDocumentInfo class loads the properties that itfinds. The LinkedDocumentInfo class reads doclink properties to get pathtranslations.

You can specify the property value as the native operating system path + "=" +http translation. The <PATH> tag is used in the properties file, and because ofproblems in specifying the : character, the : character is permitted in the database.

The table provides an example of properties for doclink path translations.

Table 10. Example of properties for doclink path translations

Current format New property name

C<PATH>\\Doclinks mxe.doclink.path1

install_home/mxadmin/DOCLINKS mxe.doclink.path2

The MaxPropValue table for doclinks contains the values listed in the table.

Table 11. Examples of values for doclink path translations

Property Value

mxe.doclink.maxfilesize 10

mxe.doclink.doctypes.defpath C:\DOCLINKS\

mxe.doclink.path1 C:\Doclinks=http://documentserver/

mxe.doclink.path2 install_home/mxadmin/DOCLINKS=http://documentserver/



Automation scripts propertiesYou can use system properties to help manage automation scripts.

Table 12. Automation script properties


mxe.script.attributelevel

Represents the maximumrelationship depth for alaunch point variable withATTRIBUTE binding type.

3 Configurationadministrator

No

mxe.script.drivers

Represents acomma-separated list ofscript drivers that is usefulwhen any custom, noneJSR223 compliant, scriptengine needs to be pluggedinto the script framework.

com.ibm.tivoli.maximo.script.JSR223ScriptDriver

Configurationadministrator

No


Bidirectional language propertiesYou can use system properties to enable and manage bidirectional languagesupport.

Table 13. Bidirectional language properties

Property DescriptionDefaultvalue Who can edit this property? Visible to tenants

mxe.bidi.support.on

Indicates whetherbidirectional support isenabled.

If the value is empty, invalidor 0, the bidirectionalsupport code is not enabled.A value of 1 indicates thatthe bidirectional support isenabled.

Tenants, system provider Yes

mxe.bidi.text.direction

When bidirectional supportis enabled, this propertyindicates that the base textdirection of text whichappears on the GUI isenforced.

The value which is enforcedis stored in this property.This property is the systemlevel property for base textdirection. There is also aMaximo business object anda Maximo business objectattribute level for the basetext direction property.

The values for this propertyare: LTR, RTL, or contextualvalues.




Bulletin board propertyYou can use the property to track viewed and unviewed messages in the bulletinboards.

The bulletin board property is PMBBISTRACKED. This property is used to set theglobal variable for bulletin boards to track viewed or unviewed messages. Thedefault value is 1.Parent topic: “Multitenancy system properties” on page 59

Calendar propertyYou can use the property to specify the system base calendar.

The calendar property is mxe.baseCalendar. This property indicates the type ofcalendar that is defined as the system base calendar. The default value isgregorian. The calendar property can be modified by the system provider and bytenants.Parent topic: “Multitenancy system properties” on page 59

Classification item propertiesYou can use classification items (CI) properties to specify data set provider classesfor CI and actual CI.

Table 14. Classification item properties


recon.engine.dataset.map.CI

Represents comma-separateddata set names that can bereconciled against CI.

ACTUAL CI Tenants, system provider Yes

recon.engine.dataset.provider.ACTUAL CI

Represents a data set providerclass for actual CI.

psdi.app.recontask.engine.dataset.ActualCIDataSet


recon.engine.dataset.provider.CI

Represents a data set providerclass for CI.

psdi.app.recontask.engine.dataset.CIDataSet



Communication template propertyYou can use the property to specify whether bind variables are ignored in thecommunication templates.

The communication template property is mxe.comm.ignoreunresolvedbindings. Thisproperty ignores unresolved bind variables in the communication templates. Thedefault value is 0. Only the configuration administrator can modify this value.Tenants can view the value.Parent topic: “Multitenancy system properties” on page 59

Condition propertyYou can use the property to list comma-separated table names that are excludedwhen the reference for a condition is checked.

The condition property is mxe.condition.excludeCheckReference. This propertyrepresents comma-separated table names that are excluded when the reference for


a condition is checked. There is no default value. This property can be modified bythe configuration administrator. It is visible to the system provider and to tenants.Parent topic: “Multitenancy system properties” on page 59

Cron task propertiesYou can use properties to manage cron tasks.

Table 15. Cron task properties

Property Description Default valueWho can editthis property?

Visible totenants

Modificationrestrictions fortenants

mxe.crontask.deleteBB Removes expired bulletinboard records.

0 Tenants, systemprovider

Yes

mxe.crontask.donotrun Use ALL to exclude all crontasks from running.

To exclude a specific cron taskfrom running, specify thecrontaskname.instancenameinstance.


Yes

mxe.crontask.historycleanuprate

Determines how often, inminutes, the excessive crontask history records areremoved.

There is no action if the valueis set to 0.


Yes The defaultvalue can onlybe reduced.

mxe.cronTaskInitDelay Represents the cron taskmonitor initialization delay inseconds.

After the system server starts,this property determines theamount of time before theserver initializes the cron task.



mxe.cronTaskMonitorInterval

Determines the time intervalsat which the cron taskmanager monitors the statusesof the cron tasks.




Database propertiesYou can use system properties to help manage the database.

Table 16. Database properties


Visible totenants


mxe.db.autocommit Represents the autocommitmode used for the Writeconnections.

This property can be eithertrue or false. The default isfalse, and you cannotchange the default value.


Yes


Table 16. Database properties (continued)


Visible totenants


mxe.db.DB2jdbcCollection

Represents the DB2 Java™

database connectivity(JDBC) collection. TheNULLIDR1 value activatesquery optimization REOPTONCE.


mxe.db.DB2LDTextCaseInsensitiveSearch

When set to 1, the DB2search on Long Descriptionfield is not case-sensitive.Might cause performancedelay.


Yes

mxe.db.DB2sslConnection

Represents the secure socketlayer (SSL) connection.

False Configurationadministrator

Yes

mxe.db.DB2sslTrustStoreLocation

Represents the DB2 SSLtruststore location.


No

mxe.db.DB2sslTrustStorePassword

Represents the DB2 SSLtruststore password.


No

mxe.db.disableservercursor

Used to disable the servercursor.

1

mxe.db.driver Represents the databasedriver.

This property must bedefined inmaximo.properties file.

com.microsoft.sqlserver.jdbc.SQLServerDriver


No

mxe.db.fetchResultLogLimit

Determines the typical orlargest fetch count for everyobject.

A stack trace is created inthe log file of theapplication server logs everytime a multiple of the fetchlog limit is reached. Forexample, if you set theproperty to 1000, the stacktrace is logged at the 1000threcord, the 2000th record,and so on.

5000

mxe.db.fetchResultStopLimit

Represents the fetch stoplimit used when checkingthat the fetch stop limit isenabled. The limit applies toall objects for which aspecific fetch stop limitproperty is not specified.

A value of -1 means thatthere is no limit.

5000

mxe.db.fetchsize

Represents the size of thedatabase fetch.


Yes The default valuecan only be reduced.

mxe.db.fetchsizeuse Represents the flag thatindicates whether to use thefetch size.


Yes




Visible totenants


mxe.db.fetchStopExclusion

Provides a comma-separatedlist of object names. If anobject name is in the list, thefetch stop limit check isdisabled for the object. If anobject name is in the list andthe same object is specifiedin anmxe.db.fetchResultStopLimit.OBJECTNAMEproperty, the exclusionoverrides the other property.

The values are representedin a comma-separated objectname list in theMAXOBJECT table.

mxe.db.fetchStopLimitEnabled

Enables or disables thechecking of the fetch stoplimit.

Use 0 to disable and use 1to enable.

1

mxe.db.format.date Determines the databasedate function.

A value of none tells thesystem to pass through thedate value.

You cannot change thisvalue.


Yes

mxe.db.format.nullvalue

Represents thedatabase-specific format ofthe null value function.

v For IBM DB2, thevalue isCOALESCE, and youcannot change thedefault value.

v For Oracle, the valueisNVL, and youcannot change thedefault value.

v For SQL Server, thevaluemust be set toISNULL.

mxe.db.format.time Represents the databasetime function.

A value of none indicatesthat the time value is passedthrough.

You cannot change thedefault value.


Yes




Visible totenants


mxe.db.format.timestamp

Represents the databasetime stamp function.

A value of none indicatesthat the time stamp value ispassed through.

You cannot change thedefault value.


Yes

mxe.db.format.upper Defines the databaseuppercase function for thesystem.


Upper Tenants,systemprovider

Yes

mxe.db.initialConnections

Represents the number ofdatabase connections thatare created when theapplication server is started.


No

mxe.db.logCorrelationid

Disables database cursorsharing. You can add thecorrelation ID as an SQLcomment. Use the propertyonly in debug mode.


No

mxe.db.logSQLPlan Represents the log executionplan for full table scans.


No

mxe.db.logSQLTimeLimit

Represents the log thatcontains the SQL operationsthat exceed the time limit inmilliseconds.



mxe.db.lookupMaxRow Represents the maximumnumber of records queriedfrom database for lookups.



mxe.db.lookupMultiplier

Used in conjunction withthe mxe.db.lookupMaxRowproperty to show items.


Yes

mxe.db.maxFreeConnections

Represents the maximumnumber of free databaseconnections that areavailable in the connectionpool.


No

mxe.db.minFreeConnections

Represents the minimumnumber of free databaseconnections that areavailable in the connectionpool.


No

mxe.db.MLQBELooseSearchWOJoin

Used for Oracle only. Do notuse outer join for search ona multiple language enabledfield.


No

mxe.db.newConnectionCount

Represents the number ofnew connections to becreated when the minimumfree connections areavailable in the connectionpool.


No

mxe.db.optionnum Represents the size of theoption.

1000




Visible totenants


mxe.db.optionuse Represents the flag thatindicates whether to use theoption.

1

mxe.db.password Represents the nativedatabase password for theMaximo connection.


XXXXXX Configurationadministrator

No

mxe.db.proxyauthentication.mode

Represents the Oracle proxyauthentication mode.

This mode is only validwhen you use Oracle ProxyDataBase Manager.

The values for thisproperty are:

v 1 = username

v 2 = username +password

v 3 = distinguishedname (DN)

v 4 = certificate


No

mxe.db.QueryTimeout Represents the amount oftime in seconds before theSQL query times out and isstopped.



mxe.db.refcount Represents the referencecount for the connection log.

100

mxe.db.resultsettype The constant indicates thetype for a result set objectwith the followingcharacteristics:

v The cursor can move onlyforward. For example:

TYPE_FORWARD_ONLYpublic static final inTYPE_FORWARD_ONLY

v The result set type that isscrollable, but notsensitive to changes thatother users make. Forexample:

TYPE_SCROLL_INSENSITIVEpublic static final intTYPE_SCROLL_INSENSITIVE

v The result set type that isscrollable and sensitive tochanges that other usersmake. For example:

TYPE_SCROLL_SENSITIVEpublic static final intTYPE_SCROLL_SENSITIVE

TYPE_FAST_FORWARD

mxe.db.retrydbconnection

Reconnects to the databasewhen you start theapplication server.


Yes




Visible totenants


mxe.db.rowcount Represents the SQL Serverrow count value.

0

mxe.db.schemaowner Indicates the databaseschema owner.


DBO Configurationadministrator

No

mxe.db.sqlinjection Indicates whether the SQLinjection check is enabled.


Yes

mxe.db.sqlserverPrefetchRows

Represents the setting toreduce lock contention andis only for SQL Server.

The optimal setting is 200rows. Setting a value largerthan 500 can degradeperformance.


Yes

mxe.db.sqlTableScanExclude

Indicates tables that shouldnot have an execution planlogged.

mxe.db.systemdateformat

Represents the system dateformat.

v For IBM DB2, thevalue iscurrent timestamp

v For Oracle, the valueissysdate, and youcannot change thedefault value.

v For SQL Server, thevalue isgetdate.


Yes

mxe.db.transaction_isolation

The installation sets thevalue to:TRANSACTION_READ_COMMITTED.


TRANSACTION_READ_COMMITTED


mxe.db.updateWithoutRowstamp

Indicates that you can allowupdates on tables that donot contain a rowstampcolumn.


No

mxe.db.url Represents the databaseURL.


jdbc:sqlserver://qadb02.swg.usma.ibm.com:1433;databaseName=SQL2K8R2B;integratedSecurity=false;


No

mxe.db.user Represents the nativedatabase user for a Maximoconnection.


maximo Configurationadministrator

No




Visible totenants


mxe.db.UseSiteListInQuery

Represents the use literal listfor site and organizationrestrictions.

0

mxe.dbmanager References the Java class ofthe Maximo databasemanager.

This property also requiresthat you specify the jdbcdatabase connection stringas the Oracle call interface(OCI) connection string, andthat you make the OCIdriver accessible to thesystem web component Javavirtual machine (JVM).

The default value ispsdi.server.DBManager.

If you have an Oracledatabasethat requires proxyauthentication,set this property topsdi.server.OracleProxyDBManager.


No

mxe.dbwatchdog.adminemail

Represents the administratoremail address used to sendthe database connectionwatchdog mail.


No

mxe.dbwatchdog.logInterval

Represents the interval timein minutes between wheneach database connectionwatchdog log is created. Thedatabase connectionwatchdog log is written tothe database connectionlogger.


Yes

mxe.dbwatchdog.mailinterval

Represents the interval inminutes before a watchdogemail is sent to theadministrator.


Yes


Deployed assets propertyYou can use the property to specify the data set provider class for deployed assets.

The deployed assets property is recon.engine.dataset.provider.DEPLOYED ASSET.This property represents the data set provider class for deployed assets. Thedefault value is psdi.app.recontask.engine.dataset.DPADataSet. The deployedassets property can be modified by the system provider and by tenants.Parent topic: “Multitenancy system properties” on page 59

Email interaction propertiesWith email interaction, users without access to a desktop can change objects andworkflow assignments. Email interaction adds system properties and each propertymust have a unique value.

System properties in the mail key

The @@MAILKEY@@ string becomes the appropriate signature string in the subject lineof emails sent to the user. For each configuration of email interaction, at least oneof the following properties is specified in the mailkey property:


Table 17. System properties in the mail key

Property DescriptionDefaultvalue

Cantenantsedit thisproperty?

Visibletotenants

Modification restrictionsfor tenants

mxe.mfmail.STSignatureSimple Identifies the configurationtype as object status changewith a simple email format.

mxe.mfmail.STSignatureAdvanced Identifies the configurationtype as object status changewith an advanced emailformat.

mxe.mfmail.WFSignatureSimple Identifies the configurationtype as workflowassignment with a simpleemail format.

mxe.mfmail.WFSignatureAdvanced Identifies the configurationtype as workflowassignment with anadvanced email format.

System properties in the email body

The following system properties are specified in the body of the emails that aresent in email interaction:

Table 18. System properties in the email body



Visibletotenants

Modificationrestrictions for tenants

mxe.mfmail.ValueListBegin

Marks the beginning of theprompt section.

mxe.mfmail.ValueListEnd

Marks the end of the promptsection.

mxe.mfmail.AssistMarker Identifies the characters thatprecede the prompt numbers.

mxe.mfmail.LineSize Indicates the line size in theemail.

72

mxe.mfmail.adminEmail Indicates the email address ofthe administrator to notifywhen errors occur that requireadministrative action. Thisproperty is optional.

System property for SMTP

The mail.smtp.starttls.enable property affects all features that send email suchas password changes


Table 19. System property for SMTP



Visibletotenants

Modificationrestrictions for tenants

mail.smtp.starttls.enable

Enables the use of theSTARTTLS command (ifsupported by the SMTPserver). The default value isfalse.


Email listener propertiesYou can use system properties to help manage email listener properties.

Table 20. Email listener properties


Visible totenants


mxe.listener.rfc822depth Represents thenumber of levelsrequired to retrieveattachments from amessage file.


Yes The defaultvalue can onlybe reduced..

mxe.listener.rfc822extension Represents the fileextension for themessage file that isdownloaded.


Yes

mxe.lsnr.validateperson Indicates whether aperson needs to bevalidated in the EmailListener application.


Yes


Environment propertiesYou can use system properties to help manage the system environment.

Table 21. Environment properties


mxe.allowLocalObjects

In productionenvironments, thisproperty is set to true toimprove systemperformance.

You set this property tofalse for developmentwork or for customapplications.



Table 21. Environment properties (continued)


mxe.enableConcurrentCheck

Allows multiple loginson the same useraccount. By default ithas a value of 0, if youwant to change thatvalue then the propertymust be defined in themaximo.properties file.

You set this property totrue (1) to preventmultiple logins on thesame user account.Before you create users,set this property to 1.


Yes

mxe.MLCacheLazyLoad

Represents themultiple-languagemetadata cache whichloads 1 object at a time.You set this property to1 to load all objectssimultaneously for 1language.


No

mxe.useAppServerSecurity

Represents the securitythat your configurationuses.

By default, the securityfor the system is used.You set this property totrue if yourconfiguration usessecurity provided by anapplication server.


Yes

mxe.UserLicenseKey

Represents the productenabler (license key) thatis used duringinstallation. If theproduct enabler changes,you must update thevalue of this property.


No


E-signature propertiesElectronic signatures confirm that a person who modifies a record is the sameperson that logged in to the system. You can use the properties to manage thee-signature feature for your organization.

Property values

The e-signature property is: mxe.esig.defaultuserid. When this property is set totrue, the default e-signature login is the login ID. The default value for thisproperty is true.



General ledger propertyYou can use the property to control the use of the upper function for the GLaccount in QBE.

The general ledger property is mxe.upperGLValues. This property controls the useof the upper function for the GL account in QBE. The default value is 0.Parent topic: “Multitenancy system properties” on page 59

Inventory propertyYou can use the property to set the maximum inventory usage line limit in aninventory usage document.

The inventory property is mxe.inventory.maxInvUseLineLimit. This propertyrepresents the maximum inventory usage line limit in an inventory usagedocument. The default value is 250. The calendar property can be modified by thesystem provider and by tenants. However, tenants can only reduce the defaultvalue.Parent topic: “Multitenancy system properties” on page 59

Issues and transfers propertyYou can use the property to open the Long Operation window when an INVISSUEis saved and the processing time is long.

The issues and transfers property is mxe.app.invissue.doLongOpOnSAVE. Thisproperty opens the Long Operation window when an INVISSUE is saved. Thereare two values: 0 that opens the HourGlass or 1 that open the Long Operationwindow. The default value is 0 The calendar property can be modified by thesystem provider and by tenants.Parent topic: “Multitenancy system properties” on page 59

Lightweight Directory Access Protocol integration propertiesYou can use system properties to manage Lightweight Directory Access Protocol(LDAP) integration.

Table 22. LDAP integration properties


mxe.allowLDAPUsers Indicates whether LDAPusers are allowed intothe system if they donot have a user record.


Yes

mxe.ClientCountMinutes

Represents the intervalin minutes for countingsessions.


Yes

mxe.LDAPMaxErrors Represents themaximum number oferrors for LDAP orvirtual machinemanager (VMM)synchronization.


No

mxe.LDAPUserMgmt Indicates whether LDAPowns user managementwhen mxe.userAppServerSecurity = 1.


Yes



maximo.properties fileYou must define system properties in the maximo.properties file to ensure that theapplication server starts. If you do not define these properties, an error message iswritten to the log file of the system or to the application server console.

Location of the properties file

The maximo.properties file is in the <Product_root>\applications\maximo\properties folder. The table lists the properties that you define in themaximo.properties file.

Table 23. maximo.properties file


Visible totenants

mxe.name Represents the applicationserver that binds theapplication server object tothe Remote MethodInvocation (RMI) registry.

MXServer Configurationadministrator

mxe.rmi.enabled Indicates whether RMI isenabled.

This property must bedefined inmaximo.properties for youto disable the property.


No

mxe.rmi.port Represents the RMIcommunication port.

If set at zero, RMI uses anyavailable port. You can selectanother available portnumber.


No

mxe.db.user Represents the database userthat the server uses to attachto the database server.

For DB2, the user must bean operating system user.

For Oracle, the user must bethe schema owner.

For SQL Server, the usermust have a systemadministrator role as definedthroughsp_addsrvrolemember. Forexample, mxe.db.user =MAXIMO.

For Oracle, the value is maximo. Configurationadministrator

No

mxe.db.password Represents the password forthe database user name.


No

mxe.db.schemaowner Represents the owner of thedatabase schema.

For DB2, the value is Maximo.

For Oracle, the value is Maximo.

For SQL Server, the value must bedbo.


No


Table 23. maximo.properties file (continued)


Visible totenants

mxe.db.url Represents the Java DatabaseConnectivity (JDBC) URL ofthe database.

ForDB2, the value is:mxe.db.url=jdbc:db2://localhost:50000/dbalias, wheredbalias is the database name.

For Oracle, the value is: mxe.db.url=jdbc:oracle:thin:@dbserver:1521:sid, where dbserveris the server name of your databaseserver, 1521 is your default Oracleport number, and sid is your Oraclesystem identifier.

For SQL Server, the value is: servername, port number, database namedefined as: mxe.db.url=jdbc:inetdae7a:servername:1433?database=databasename&language=us_english&nowarnings=true, in whichdatabasename represents the databasename, servername represents thename of the server, and 1433represents the default SQL Serverport number. The string mxe.db.url=jdbc:inetdae can be followed byeither 7 (supports Unicode) or 7a(supports ASCII). Currently, onlyASCII for SQL Server is supported.


No

mxe.db.driver Represents the thin driverdefined in mxe.db.driver.

For DB2, the value is:mxe.db.driver=com.ibm.db2.jcc.DB2Driver

For Oracle, the value is:mxe.db.driver=oracle.jdbc.driver.OracleDriver

For SQL Server, the value is:mxe.db.driver=com.inet.tds.TdsDriver


No

mxe.enableConcurrentCheck

Allows multiple logins onthe same user account. Youset this property to true (1)to prevent multiple logins onthe same user account.

Before you create users, setthis property to 1.


Yes


Migration Manager propertiesYou use Migration Manager to migrate configuration content from one productenvironment to another. You can use the properties to control the migration of theconfiguration content.


Table 24. Migration Manager properties



mxe.dm.autoapprovepkgdef

Represents theMigrationManager autoapproval ofpackagedefinitions.


Yes

mxe.dm.collvalidlevels Represents themaximum numberof levels searchedto find relatedrecords.


Yes The default valuecan only bereduced.

mxe.dm.collvalidsrcexclude

Specifies thesource object,attribute, andvaluecombinations thatcannot betraversed to.

MAXINTOBJCOLSMAXINTOBJALIAS

mxe.dm.collvalidtgtexclude

Specifies the targetobject andattributecombinations thatcannot betraversed fromduring validation.

MAXINTOBJECT.USEWITH,MAXRELATIONSHIP.CARDINALITY,CRONTASKINSTANCE.SCHEDULE

mxe.dm.continueonerror

Continues theMigrationManagerdeployment whenan error is found.


Yes

mxe.dm.dbserver Represents thedatabase servername for Oracle9.x.


No

mxe.dm.dmroot Represents thename of theMigrationManager rootfolder that is onthe applicationserver computer.This folder storesMigrationManager packagefiles.

You mustconfigure thisproperty beforeusing MigrationManager.


Yes


Table 24. Migration Manager properties (continued)



mxe.dm.dmsessiontimeout

Represents thetimeout value ofthe MigrationManager HTTPsession in minutes.

When along-runningMigrationManager task(such as packagecreation orpackagedeployment)starts, the timeoutvalue for thesession of the userwho is currentlylogged in changesto the valuespecified by thisproperty.


Yes The default valuecan only bereduced.

mxe.dm.dmstagecommit

Specifies thecommit intervalfor records thatare inserted intothe staging tablein the targetenvironment forthe MigrationManager.

The value isspecified in thesourceenvironment, andMigrationManager uses thevalue whendistributing apackage from thesource database tothe targetdatabase.

1

The default valueindicates that thecommit intervaloccurs for every (1)record.


Yes

mxe.dm.importlimit

Represents thecollection importlimit.

100

mxe.dm.previewfreememorythreshold

Represents thememory thresholdin percentagebefore the previewoperation stops.


Yes


mxe.help propertiesThe mxe.help system properties connect the user interface to the informationcenter. Some of the properties are used to construct the link that opens theinformation center. To ensure that information center is available, match the valuesin the mxe.help properties to the information center that you deploy.


Table 25. Information center properties


Visible totenants

mxe.help.host Represents thehost name or IPaddress of theinformationcenter.

127.0.0.1 Configurationadministrator

No

mxe.help.maximohelplink

Represents thetop-level helplink. The propertymust match theevent values inthe menus.xml file.

com.ibm.mam.doc,welcome.html


No

mxe.help.path Represents thepath that isinserted betweenthe informationcenter port andthe topic whenthe link to theinformationcenter isconstructed.

/help/ Configurationadministrator

No

mxe.help.port Represents theport of theinformationcenter.


No

mxe.help.protocol Represents theprotocol of theinformationsystem (HTTP orHTTPS).

http Configurationadministrator

No

mxe.help.viewsearchtiplink

Represents theplug-in name andfile name linkedto View SearchTips, which isavailable from theList tab of mostapplications

com.ibm.mbs.doc,mbs_common/c_advanced_search_tips.html


No


OSLC propertiesYou can use system properties to help manage Open Services for LifecycleCollaboration (OSLC) application integration.

Table 26. OSLC properties


mxe.oslc.dfltversion Represents the default OSLC version for an OSLCprovider.

2

mxe.oslc.prcreateep Represents the Provider Registry Create Endpoint.

mxe.oslc.prqueryep Represents the Provider Registry Query Endpoint PROVIDERREGISTRY

mxe.oslc.webappurl Represents the Provider Public URL. http://localhost/maximo/oslc/



Reorder propertyYou can use the reorder property to manage the reorder time out periods for yourorganization.

The reorder property is mxe.reorder.previewtimeout. This property represents thereorder preview time out period in minutes. This property is similar to the webserver session time out. The default value is 30 minutes. The calendar property canbe modified by the system provider and by tenants. However, tenants can onlyreduce the default value of the reorder property.Parent topic: “Multitenancy system properties” on page 59

Report integration propertiesYou can use report properties to control how reports are created and managed. Youcan identify all the report properties if you specify report as a filter value in theDescription field.

Table 27. Report properties


Visible totenants


mxe.activex Determines ifActiveX Controlscan be used forDirect Print (DP)and Direct PrintwithAttachments(DPA).

Enables printingof attacheddocuments thatare Microsoft filetypes (such as.xls, .doc, .ppt).

If you do notwant to enableActive XControls to printMicrosoftdocuments, youmust set thevalue to N (0),then Microsoftdocuments arenot used withDPA.


Yes


Table 27. Report properties (continued)


Visible totenants


mxe.directprint.inherited.attachments

Defines ifinheriteddocuments areenabled forprinting by usingthe Direct PrintwithAttachmentsfunction.

Used for directprint withattachments.



mxe.directprint.javaconsole.debug

Enables you tooutput to JavaConsole fortroubleshooting.


Yes

mxe.directprint.printtime.waitinminutes

Indicates themaximumduration thecurrent printprocess shouldwait beforebailing out.



mxe.report.AttachDoc.validateURL

Determines if theURL of theattacheddocument needsto be validatedbefore printingthe documentfrom the V7Server.


Yes

mxe.report.birt.disablequeuemanager

Defines whetherthe queuemanager isenabled. If thequeue manageris disabled(value set to 1),scheduledreports are notrun on theserver.

Used formulti-serverconfigurations,performancemaintenance.


No




Visible totenants


mxe.report.birt.maxconcurrentrun

Manages thenumber ofimmediate andscheduledBusinessIntelligenceReporting (BIRT)reports that canbe runconcurrently

Used forperformancemaintenance.


Yes

mxe.report.birt.queueidletimeseconds

Frequency, inseconds, that thequeue managerpolls the queuefor new reportjobs.

Used forperformancemaintenance.


Yes

mxe.report.birt.viewerurl

Represents theBIRT ViewerURL forclustered orseparate reportservers, forexample: http://myhost:myport/maximo/report

Used for BIRTReport OnlyServer (BROS)configuration


No

mxe.report.adhoc.editWithGroupAccess

Enables you toedit an ad hocreport when anysecurity grouphas access to thereport.


Yes

mxe.report.cognos.content.store.package.location

Represents thecontent storefolder where theCognos packageis published.


No

mxe.report.cognos.datasource

Represents theMaximo datasource name thatis used by theCognos adapter.


No

mxe.report.cognos.db.schemaName

Represents theMaximodatabase schemaname that isused by theCognos adapter.


No




Visible totenants


mxe.report.cognos.db.sql.name

Represents theMaximodatabase namewhere thedatabase type isSQL-Server.


No

mxe.report.cognos.db.type

Represents theMaximodatabase typethat is used bythe Cognosadapter.


No

mxe.report.cognos.namespace

Represents theCognosnamespacewhich holdsinformationabout users,security groups,and roles.


No

mxe.report.cognos.serverURL

Represents theCognosdispatcher/gateway URI.The property isused to launchCognos reportsoradministration.


No

mxe.report.custom.rptServerLogonPass

Represents thepassword usedto log on to theexternal reportserver.


No

mxe.report.custom.serverURL

Represents theURL for customreportapplications.


No

mxe.report.reportsInAPage

Defines thenumber ofreports thatdisplay in theReport window.


Yes

mxe.doclink.defaultPrintDocWithReport

Represents thedefault value forprinting anattacheddocument withreport ifprintable type.

Used for directprint withattachments.

True Tenants, systemprovider

Yes


Additional report properties

Depending on your external reporting system, you might need to specifyadditional property values. You can add properties in the System Propertiesapplication.Parent topic: “Multitenancy system properties” on page 59

Security propertiesThe data types Crypto and CryptoX are used to encrypt passwords and othertypes of confidential information. You use security properties to specify securitylevels for your organization, such as the data that must be encrypted and can bedecrypted.

CRYPTO and CRYPTOX parameters

Parameters identified as mxe.security.crypto are for the CRYPTO maxtype. Theseparameters identify the attributes that can be encrypted and decrypted.

Parameters identified as mxe.security.cryptox are for the CRYPTOX maxtype.These parameters identify the attributes that can be encrypted, but not decrypted.These maxtypes have their own means of encryption, the parameters for which aredefined in the properties file.

Table 28. Security properties

Property Description Default valueWho can edit thisproperty?

Visible totenants

mxe.sec.adduser.maxsets Represents the maximumnumber of concurrent setsallowed for user selfregistration.


Yes

mxe.sec.forgotpassword.maxsets Represents the maximumnumber of concurrent setsallowed for a forgottenpassword.


Yes

mxe.sec.IPblock Performs security checks relatedto IP blocking.


Yes

mxe.sec.IPblock.MatchBoth Matches both the client host andthe client address when youcheck for clients that areblocked.


Yes

mxe.sec.IPblock.num Represents the maximumnumber of incorrect loginattempts allowed per number ofseconds.


Yes

mxe.sec.IPblock.sec Represents the time in secondsrequired for the IP blockinglimit check.


Yes

mxe.security.crypto.algorithm Identifies the attributes that canbe encrypted and decrypted.

Algorithm is the basic type ofencryption that is used.

This property can override thealgorithm default value DESed.


No


Table 28. Security properties (continued)


Visible totenants

mxe.security.crypto.key Identifies the attributes that canbe encrypted and decrypted.

The length of this property mustbe a multiple of 24.


No

mxe.security.crypto.mode Identifies the attributes that canbe encrypted and decrypted.

The following modecomponents are valid:

v Cipher Block Chaining Mode(CBC) as defined in FIPS PUB81.

v Cipher Feedback Mode (CFB)as defined in FIPS PUB 81.

v Electronic Codebook Mode(ECB) as defined in TheNational Institute of Standardsand Technology (NIST) FederalInformation Processing Standard(FIPS) PUB 81, DES Modes ofOperation, U.S. Department ofCommerce, Dec 1980.

v Output Feedback Mode (OFB)as defined in FIPS PUB 81.OFB must use NoPadding.

v Propagating Cipher BlockChaining (PCBC) as definedby Kerberos V4.


No

mxe.security.crypto.modulus Identifies the attributes that canbe encrypted and decrypted.

Modulus is used only for theRSA algorithm.


No

mxe.security.crypto.padding Identifies the attributes that canbe encrypted and decrypted.

The following paddingcomponents are valid:

v NoPadding - No padding.

v PKCS5Padding - The paddingscheme described in RSALaboratories, PKCS #5:Password-Based EncryptionStandard, version 1.5, November1993.


No

mxe.security.crypto.spec Identifies the attributes that canbe encrypted and decrypted.



No

mxe.security.cryptox.algorithm Identify the attributes that canbe encrypted, but not decrypted.

Algorithm is the basic type ofencryption that is used.

This property can override thealgorithm default value(DESede).


No




Visible totenants

mxe.security.cryptox.key Identify the attributes that canbe encrypted, but not decrypted.



No

mxe.security.cryptox.mode Identify the attributes that canbe encrypted, but not decrypted.

The following modecomponents are valid:

v Cipher Block Chaining Mode(CBC) as defined in FIPS PUB81.

v Cipher Feedback Mode (CFB)as defined in FIPS PUB 81.

v Electronic Codebook Mode(ECB) as defined in TheNational Institute of Standardsand Technology (NIST) FederalInformation Processing Standard(FIPS) PUB 81, DES Modes ofOperation, U.S. Department ofCommerce, Dec 1980.

v Output Feedback Mode (OFB)as defined in FIPS PUB 81.OFB must use NoPadding.

v Propagating Cipher BlockChaining (PCBC) as definedby Kerberos V4.


No

mxe.security.cryptox.modulus Identify the attributes that canbe encrypted, but not decrypted.

Modulus is used only for theRSA algorithm.


No

mxe.security.cryptox.padding Identify the attributes that canbe encrypted, but not decrypted.

The following paddingcomponents are valid:

v NoPadding - No padding.

v PKCS5Padding - The paddingscheme described in RSALaboratories, PKCS #5:Password-Based EncryptionStandard, version 1.5, November1993.


No

mxe.security.cryptox.spec Identify the attributes that canbe encrypted, but not decrypted.



No




Visible totenants

mxe.security.provider Represents the security providerwhich is obtained from thepolicy file. The security provideris usuallycom.ibm.crypto.provider.IBMJCE.

To use a different provider, youcan specify a value for thisparameter.


No


Server propertiesYou can use the server properties to control how a server operates, such asspecifying values for the administration user, for user registration, and emailauthentication.

Table 29. Server properties


Visible totenants

mail.smtp.host Represents the name ofthe host that runs theSMTP server.

This name is needed forfacilities that use emailnotifications, such asworkflow notifications,email, and any errormessage notifications.Your networkadministrator can providethis address.

na.relay.ibm.com Configurationadministrator

No

mail.smtp.sendpartial Indicates that partialemails are sent to validemail addresses.


Yes

mail.smtp.ssl.enable Enables SSL over SMTP. FALSE

mail.smtp.starttls.enable Enables STARTTLS overSMTP.

FALSE

maximo_extended_host Represents the Maximoextended host.

maximo_extended_host_protocol Represents the Maximoextended host protocol.

mxe.adminEmail Represents the emailaddress that is used if theuser does not specify anemail address in the laborrecord.

This value is requestedduring installation.


Yes


Table 29. Server properties (continued)


Visible totenants

mxe.adminmode.logoutmin Represents the number ofminutes that users mustlog out before theapplication server isplaced in Admin mode.Admin mode is used toconfigure the database(including the applicationof structural changes).


No

mxe.adminmode.numsessions Represents the number ofadministrative sessionsthat are allowed after theapplication server isplaced in Admin mode.


No

mxe.adminPasswd Represents the passwordfor the administrativeuser.

maxadmin

mxe.adminPassword Represents the passwordfor the administrativeuser.

maxadmin, thesystem login ID ofthe administrativeuser.


Yes

mxe.adminusercredential Represents the credentialof the administrativeuser.


Yes

mxe.adminuserid Represents theadministrative user. Thisuser must have access toall sites.

The server uses thisproperty foradministrative tasks andto run cron tasks.

maxadmin Tenants, systemprovider

Yes

mxe.adminuserloginid Represents the systemlogin ID for theadministrative user.

maxadmin Tenants, systemprovider

Yes

mxe.com.port Represents the com port.

mxe.convertloginid This property identifieswhether the login id thatthe user entered must beconverted to uppercasebefore it is validated.

For conversion, set thevalue to 1.

0 - do not convert Tenants, systemprovider

Yes

mxe.email.charset Represents the characterset for email notificationsthat are sent.

When this property isdefined, the character setis used to encode thesubject and the messagewhen an emailnotification is sent. Fornon- Englishenvironments, you mustset the UTF-8 character.




Visible totenants

mxe.email.content.type used to set the contenttype for allcommunications.

text/html

mxe.hostname Represents the name ofthe workstation and portthat hosts the MXServer.

localhost:7001 Configurationadministrator

No

mxe.maxsequencecheck Indicates whether tocheck for multiplesequence values beforeusing.


No

mxe.registry.bindcount Represents the retrycount for the systemRemote MethodInvocation (RMI) registrybinding.

When the system serverstarts and it runs intoregistry bind failures, theserver tries to start forthe number of attemptsspecified in this property.


mxe.registry.port Represents the serverRMI registry port that theserver components uses.


mxe.retainrecord Retains the state of theapplication tab childtables during editing (lessthan retainreclimit).


Yes

mxe.retainrecordlimit Represents the maximumnumber of records forwhich the table can retainits state.

A higher number canaffect performance.

Tenants can only reducethe default value of thisproperty.


Yes

mxe.smtp.connectiontimeout Represents the socketconnection timeout valuein milliseconds.


No

mxe.smtp.password Defines the password foremail authentication. Thisproperty must be usedwith mxe.smtp.userproperty.

Null - disablesemailauthentication.


No

mxe.smtp.timeout Represents the socket I/Otimeout value inmilliseconds.


No

mxe.smtp.user Defines the user ID foremail authentication. Thisproperty must be usedwith mxe.smtp.passwordproperty.

Null - disablesemailauthentication.





Visible totenants

mxe.system.DomainFactoryNameProvider

Represents the class paththat provides theDomainInfoFactory classnames used wheninitializing domains.

psdi.mbo.DomainFactoryNameProvider

mxe.system.regpassword Represents the userregistration loginpassword.


maxreg Configurationadministrator

No

mxe.system.reguser Represents the userregistration login name toregister a user. The username that is specifiedmust have authorizationto create new users.


maxreg Configurationadministrator

No

mxe.usermonitor.InactiveSessionTimeLimit

Represents the time aninactive session remainsin the MAXSESSIONtable.

120

mxe.usermonitor.timeout

Represents the sessiontimeout period, inminutes, on the server toclear the cache.


Yes

mxe.userrestrictionlrucachesize

Manages the number ofentries in the LRU cachethat stores the restrictionentries.


No

WAS.LTAURL Represents the URL usedto launch the Log andTrace Analyzer.

/ibm/action/launch?pageID=com.ibm.ac.lta.web.ui.LogAnalyzer&showNavArea=false

mxe.server.enableCSRFBlocking Enables checks for theCSRF security token.


Yes

mxe.service.runlist Representscomma-delimited servicesthat must be run.

mxe.sessiontoken.timeoutseconds Represents a token-basedsession timeout inseconds. This token isused when the user ID isbeing authenticated onthe report server.

The session token timeoutsetting code is genericand currently only BIRTReporting uses thisfunction.

Used for BIRT ReportOnly Server (BROS)configuration

180 seconds Configurationadministrator

Yes



Utilities for logging and testingTo help you manage system performance, there are utilities that you can use fortesting and debugging purposes. When you are satisfied with your deployment,you can disable these logging utilities.

Utilities that track system performance

By default, the mbocount logging utility, the logSQLTimeLimit logging utility, andthe fetchResultLogLimit logging utility are enabled in the properties file. Theseutilities enable you to track the following possible system performance issues whileconfiguring an initial system deployment:v Excessive use of business objectsv Slow execution of SQL statementsv High number of records returned in a query result

To disable the logging utilities, change the debugging properties described in thetable.

Table 30. Debugging properties


Visible totenants

mxe.mbocount Displays the number ofbusiness objects that the servercreated.

To disable, change the value ofthe property to 0.


No

mxe.db.logSQLTimeLimit Represents the SQL statementsthat take longer than thespecified time limit are logged.The time is measured inmilliseconds.


Tenants can only reduce thedefault value.


Yes

mxe.db.fetchResultLogLimit When this property is enabled,a stack trace is printed in thelog for every business objectset that fetches beyond the setlimit of rows. The stack tracelog is also repeated for everymultiple of such fetches.


1000 rows


Table 30. Debugging properties (continued)


Visible totenants

mxe.db.logSQLPlan (Oracle only) Setting this property to truelogs the execution plan for allSQL statements that contain afull table scan.

If you definemxe.db.sqlTableScanExclude,all tables, except for the onesyou intentionally exclude, arelogged.

If you do not definemxe.db.sqlTableScanExclude,only the SQL statements thatexceed the time limit set inmxe.dblogSQLTimeLimit are logged.


No

mxe.db.sqlTableScanExclude=ACTION,MAXROLE,SCCONFIG,MAXUSER (Oracle only)

You can define the table namesthat you want to exclude fromthe log. The table names mustbe uppercase.

If you definemxe.db.sqlTableScanExclude,all tables, except for the onesthat you list, are logged.

If you do not definemxe.db.sqlTableScanExcludeand you setmxe.db.logSQLPlan=true,only the SQL statements thatexceed the time limit set inmxe.dblogSQLTimeLimitare logged.

0

mxe.logging.CorrelationEnabled

Represents the correlation IDthat is logged if a percentageof the queue is specified in thelogger layout.


No

mxe.logging.disableLoggingPropFile

Allows you to disable thelogging.properties file forlogging.


Yes

mxe.logging.rootfolder

Represents the default rootfolder to where Maximogenerated log files are written.


No


Work order generation propertyYou can use to use a property to manage the generation of work orders.

The work order generation property is mxe.msgLogFile. This property representsthe log file for work order generation. The configuration administrator can modifythis property. However, tenants and the system provider can view the property.Parent topic: “Multitenancy system properties” on page 59


Chapter 7. PDF documentation

This information center includes documentation in PDF format. In some cases, thecontent also appears in the information center as HTML topics; the PDF documentsare provided as a convenience.

Table 31. PDF documentation

Title DescriptionLink to topics ininformation center

Administering the System Provides information forsystem providers,configurationadministrators, andtenants on the featuresof amultitenancy-enabledproduct.


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

U.S.A.IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

COPYRIGHT LICENSE: This information contains sample application programs insource language, which illustrate programming techniques on various operatingplatforms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM, for the purposes of developing, using, marketing ordistributing application programs conforming to the application programminginterface for the operating platform for which the sample programs are written.These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of anykind. IBM shall not be liable for any damages arising out of your use of the sampleprograms.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other product and service names might be trademarks of IBM or other companies.

Notices 101

��

Printed in USA

maximo 7.5 multi tenancy db2

Software