sp430_client_types
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
Â
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. |