IBM BPM, V8.0.1, All platforms > Migrating and upgrading your IBM BPM environment > Migrating from other products > Migrating from WebSphere InterChange Server or WebSphere Business Integration Server Express > Premigration considerations

Premigration considerations: Business objects

For the development of business objects, use only the tools provided to configure artifacts, use explicit data types and lengths for data attributes, and use only the documented APIs.

Business objects within IBM BPM are based on service data objects (SDOs). SDOs use data attributes that are strongly typed. For business objects in WebSphere InterChange Server or WebSphere Business Integration Server Express and adapters, data attributes are not strongly typed, and users sometimes specify string data types for non-string data attributes. To avoid issues in IBM BPM, explicitly specify data types. You can set these either in the WebSphere Business Integration (WBI) Toolset before migration or in IBM Integration Designer. Failure to define data types explicitly might result in nondeterministic behavior.

Because business objects within IBM BPM might be serialized at run time as they are passed between components, it is important to be explicit with the required lengths for data attributes in order to minimize the use of system resources. For this reason, do not use the maximum 255-character length for a string attribute, for example. Also, do not specify zero-length attributes that currently default to 255 characters. Instead, specify the exact length required for attributes.

XSD NCName rules apply to business object attribute names in IBM BPM. Do not use any spaces or ":" in names for business object attributes. Business object attribute names with spaces or ":" are not valid in IBM BPM. Rename business object attributes before migration.

If using an array in a business object, you cannot rely on the order of the array when indexing into the array in Maps or Relationships.

The construct that this migrates into in IBM BPM does not guarantee index order, particularly when entries are deleted.

It is important to use only the Business Object Designer or the Business Object Designer Express tool to edit business object definitions, and to use only the published APIs for business objects within integration artifacts.

: Premigration considerations