Ibm WebSphere Adapters Bedienungsanleitung Seite 78
- Seite / 226
- Inhaltsverzeichnis
- FEHLERBEHEBUNG
- LESEZEICHEN
Bewertet. / 5. Basierend auf Kundenbewertungen
Convert business object names from EIS-assigned formats to a camel case format
(remove separators such as spaces or underscores and capitalize first letter of each
word). For example, convert the EIS name, ORDER_LINE_ITEM, to OrderLineItem.
As described in the WebSphere business object specification, name the parent
business object graph for the contained business object followed by BG. For
example, CustomerBG is the parent object graph for a Customer business object.
Business objects names as well as property names should have no semantic value
to the adapter. When you develop your adapter logic, be sure that it is based on
metadata as opposed to naming conventions.
Standard operations:
As described by the JCA specification, a resource adapter is generally intended to
expose low-level, EIS-specific operations. These EIS-specific operations range from
create, retrieve, update, and delete (for database-type applications) to those that are
unique to customer EIS instances (for function-based adapters such as SAP).
The WebSphere business object model and a variety of WebSphere components
(such as the relationship management service) assume that most adapters support
a set of standard create, retrieve, update, and delete operations. This leaves a gap
for most adapters where the supported low-level operations do not natively meet
the expectations of other WebSphere components. To fill this gap, all adapters
should support higher-level create, retrieve, update, and delete operations,
depending on what is provided by the EIS. With such support, a Create operation
for one adapter follows the same naming conventions and behavior as a Create
operation for another adapter. The result is better tooling and consistency in terms
of user experience.
The following are the supported, standard top-level operations:
Supported standard top-level operations
Inbound Operation Signatures Notes
emitCreateAfterImage<BOType>
emitUpdateAfterImage<BOType>
emitDeleteAfterImage<BOType>
These operations should generate
after-image business objects with verbs that
match the operation signature; for example,
emitCreateAfterImageCustomer should
generate a Customer object with verb Create.
emitDelta<BOType> This operation should generate a delta
business object with a summary depicting
the changes that occurred in the EIS.
72 WebSphere Adapters: WebSphere Adapter Toolkit User Guide
- WebSphere 1
- Contents 5
- WebSphere Adapter Toolkit 7
- IBM WebSphere Adapters 8
- Business 9
- Architectural overview 10
- JCA connector component 11
- Metadata 13
- Operating system requirements 17
- Samples overview 18
- Developer 19
- Modify the module 30
- Test the sample 31
- Troubleshooting the samples 34
- Specify project properties 37
- Specify project facets 38
- Specify generation options 40
- Data Binding classes 44
- Using the Overview pane 64
- Generated bean properties 73
- Data model 75
- After-images versus deltas 76
- Verbs versus operations 77
- Business object standards 77
- Inbound event notification 85
- Event Store Requirements 87
- Adapter Requirements 87
- Application Requirements 87
- Transaction Support Methods 93
- One way callback events 96
- Callback event sender 97
- Outbound support 103
- Application sign-on 104
- Implementing outbound support 105
- Using command patterns 111
- Data and metadata 121
- The Metadata API 125
- Factory classes 126
- Interfaces 126
- Interface Type: 127
- Types of enterprise metadata 130
- Metadata discovery 133
- OutboundConnectionType 134
- InboundConnectionType 135
- MetadataConnection 136
- Namespace definition 142
- Implementing a data handler 164
- Implementing a data binding 165
- Discovery-service.xml 168
- Initialize input method 169
- Initialize output method 169
- Set managed connection method 170
- Get next method 170
- Clone method 171
- Close method 171
- Extract method 171
- Data binding implementation 172
- DataBinding generator 173
- Problem determination 174
- Logging and tracing messages 180
- Validating the code 199
- Developing JUnit tests 201
- Installing the test client 204
- Saving business object data 205
- Using an execution trace 206
- Testing inbound functionality 206
- WebSphere Application Server 209
- Reference 214
- Terminology 214
- Trademarks and service marks 219
- Printed in USA 226
Verwandte Produkte und Handbücher für Hardware Ibm WebSphere Adapters
Hardware Ibm 22P6959 Bedienungsanleitung
(50 Seiten)
(50 Seiten)
Hardware Ibm Ultra320 Bedienungsanleitung
(54 Seiten)
(54 Seiten)
Hardware Ibm 09-0572-000 Bedienungsanleitung
(101 Seiten)
(101 Seiten)
Hardware Ibm EP-8KTA Bedienungsanleitung
(73 Seiten)
(73 Seiten)
Hardware Ibm 28L2234 Bedienungsanleitung
(66 Seiten)
(66 Seiten)
Hardware Ibm 71P7285 Bedienungsanleitung
(77 Seiten)
(77 Seiten)
Hardware Ibm CFC2 Bedienungsanleitung
(154 Seiten)
(154 Seiten)
Hardware Ibm 2292 Bedienungsanleitung
(230 Seiten)
(230 Seiten)
Hardware Ibm x Series 200 Bedienungsanleitung
(152 Seiten)
(152 Seiten)
Hardware Ibm 48X-20X Bedienungsanleitung
(50 Seiten)
(50 Seiten)
Hardware Ibm THINKPAD 2000 Bedienungsanleitung
(88 Seiten)
(88 Seiten)
Whirlpool GC751TX manuály
Uživatelské manuály a uživatelské příručky pro Sporáky Whirlpool GC751TX.
Poskytujeme 1 manuály pdf Whirlpool GC751TX ke stažení zdarma podle typů dokumentů: Návod k použití
Kommentare zu diesen Handbüchern