This table contains the set of different types of client that may communicate with the ServiceOptimizer instance and the password that they should use. The table has the following data added to it

A client whose type does not exist in this table will be rejected. A client whose type has a password of null will need to login using the database password.

Important for the API SOAP calls both API and APIAproxy need to have the same values. So if API has a password 'fiona' then APIAproxy also needs a password of 'fiona'. If this is not the case some of the SOAP API calls will fail with an 'invalid logon' message.

This MUST be the same at ALL SITES:

#	Name	Password
1	'API'	Null
2	'DAA'	Null
3	'Gantt'	Null
4	'APIAproxy'	Null

Table Definition

Field	Type	Default	Nullable
client_type_no	number(9)
description	varchar2(50)
password	varchar2(50)

Keys

primary key (client_type_no)

Primary Key Referenced From

sp431_client_server_map

Column Descriptions

Field	Description
client_type_no	Unique identifier of client type.
description	Textual description of the client.
password	Password that authorises clients of this type. If null, will default to the database schema password.

ServiceScheduling 13.3

sp430_client_types

Analytics

Table Definition

Keys

Primary Key Referenced From

Column Descriptions

Related content