Table 21 details the general features supported by the
connector.
Category | Feature | Support | Notes |
---|---|---|---|
Business object attributes | Foreign key | No |
|
| Foreign key attribute property | N/A |
|
| Key | No |
|
| Max length | Partial | This attribute applies when formatting business objects to fixed-sized records. |
| Meta-data-driven design | Full | The JText connector supports any business objects supported by IBM WebSphere Business Integration Adapter Framework. However, some formatters and data handlers have specific requirements for application text, business object structure, and so on. If these formatters or data handlers are used, only business objects that meet those requirements can be successfully processed by the JText connector. |
| Required | Partial |
|
Connection Lost | Connection lost on poll | Partial |
|
| Connection lost on request processing | Partial |
|
| Connection lost while idle | Partial | In certain conditions (such as an IO error), JText sends APPRESPONSE_TIMEOUT. |
Connector Properties | ApplicationPassword | No |
|
| ApplicationUserName | No |
|
| UseDefaults | Full |
|
Message Tracing | General messaging | Full |
|
| generateMsg() | Full | All trace messages are hard-coded. |
| 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 | No |
|
| Java Package names | Full |
|
| Logging messages | Full | All known error conditions are taken care of. |
| NT service compliance | Full |
|
| Transaction support | N/A |
|
Special Value | CxBlank processing | N/A | Data handler dependent. |
| CxIgnore processing | N/A | Data handler dependent. |