Table 14 details the general features supported by the
connector.
Category | Feature | Support | Notes |
---|---|---|---|
Business Object Attributes | Foreign key | No |
|
| Foreign Key attribute property | No |
|
| Key | Full | Key attributes are used for object retrieval. |
| Max Length | No |
|
| Meta-data-driven design | Full |
|
| Required | Full | The connector fails a Create operation if a business object does not have a valid value or a default value for a Required attribute. |
Connection Lost | Connection lost on poll | Full |
|
| Connection lost on request processing | Full |
|
| Connection lost while idle | Full |
|
Connector Properties | ApplicationPassword | Full |
|
| ApplicationUserName | Full |
|
| UseDefaults | Full |
|
Message Tracing | General messaging | Partial | Tracing approximates the specified levels. |
| generateMsg() | Partial | Generate message is used for some tracing. |
| Trace level 0 | Partial |
|
| Trace level 1 | Partial |
|
| Trace level 2 | Partial |
|
| Trace level 3 | Partial |
|
| Trace level 4 | Partial |
|
| Trace level 5 | Partial |
|
Misc. | CDK method LogMsg | Partial | Some strings are hard coded. |
| Java Package Names | N/A |
|
| Logging messages | Full |
|
| NT service compliance | Full |
|
| Transaction support | No | For the connector, a transaction is not defined as an operation on a complete hierarchical business object. Instead, the connector defines a separate transaction for each operation on individual parent or child business objects in a hierarchical business object. When the connector receives a business object with a Create verb, it first processes the parent business object and then processes each individual child business object. Under normal conditions, the connector begins a transaction for each business object in the hierarchy, creates the entity in the application, and commits the transaction. If the connector succeeds in creating one or more child entities, and a failure occurs during the creation of another child entity, the connector rolls back the Create operation for this particular business object by backing out the entity. The connector continues processing child business objects until all the remaining entities have been created. Because there was a failure, the connector returns FAIL to the integration broker for the overall operation on the business object. In addition, the Create or Update operation in the application may be incomplete. This scenario is similar for an Update transaction. |
Special Value | CxBlank processing | Full |
|
| CxIgnore processing | Full |
|