Release notes. IBM Industry Models IBM Banking/Insurance Process and Service Models for Standard Tooling - Utilities Version

Transcription

1 Release notes IBM Industry Models IBM Banking/Insurance Process and Service Models for Standard Tooling - Utilities Version

2 Contents About these release notes... 1 Fixes since the previous release... 1 Known issues and limitations... 1 Known IBM Rational Software Architect issues and limitations... 3 Known IBM Business Process Manager issues and limitations... 4

3 About these release notes These release notes address defect fixes, known product issues and workarounds relating to the product. Further product documentation is included in the Information Center, which is installed with the product. Fixes since the previous release Reference MD00096 Description Rational Software Architect (RSA) utilities require.emx files to be in the root of the project. In the non-customized Industry Models BPS/IPS for Standard Tooling RSA projects, the.emx files (the UML models) are in the root of the project. Previously, if the.emx files were moved into a subfolder in the project, the Industry Models RSA utilities did not work Analysis Process Model (APM) to Orchestration Process Model (OPM) Transform OPM processes have no documentation. Previously, OPM processes created by the APM-to-OPM transform had no documentation APM-to-OPM transform cannot create user tasks. Previously, if you selected Create UserTasks for non-automatable GlobalTasks in the APM-to-OPM wizard, the APM-to-OPM transform failed RSA utilities cannot be invoked from a UML diagram. Previously, the Industry Models RSA utilities could not be invoked by selecting an appropriate element in a UML diagram, right-clicking on the diagram element and selecting one of the Industry Models menu options Transfer objects that are created from association classes have spaces in their names. Previously, transfer objects created from association classes by the transfer object generation utility had spaces in their names. Known issues and limitations Reference Description The transfer object generation utility does not detect invalid Interface Design Model (IDM) attribute types. Currently, the transfer object generation utility does not detect invalid IDM attribute types, such as BOM Enumeration or BOM Primitive, and incorrectly processes them, resulting in transfer object attributes with invalid types, which can cause problems when you generate WSDL and XSD files. Workaround: regularly validate IDM and Transfer Object Model (TOM) to ensure that attributes have valid types The transfer object generation utility does not create attributes for explicitly selected type interface parameters. Explicitly selected parameters in the Create a Transfer Object from an IDM Class wizard page are not created as transfer object attributes. Workaround: select a type interface operation to create transfer object attributes for all out parameters of the operation Industry Models SOA Validation constraints must allow for the use of subtypes of RequestHeader and ResponseHeader. SDM Service Parameter <<MessageType>> data types must have a request/response attribute of the RequestHeader/ResponseHeader type. Currently, if you create subtypes of RequestHeader or ResponseHeader and use these as the types of the SDM Service Parameter <<MessageType>> data type attributes, when you validate the SDM warnings will display stating that these attributes must be of the RequestHeader/ResponseHeader type. Workaround: disable the following Industry Models validation constraints in Preferences in RSA: Request SDM Service Parameter MessageType must contain an attribute of the RequestHeader type Response SDM Service Parameter MessageType must contain an attribute of the ResponseHeader type 1

4 Reference Description Add SOAP fault exception parameters to SDM ServiceInterface operations. SDM ServiceInterface operations can contain three parameters: A Request in parameter A Response out parameter A SOAP Fault Exception Parameter SOAP fault exception parameters are created as SOAP faults in the generated WSDL files, and these enable a better error handling strategy for your SOAP services: Information about minor issues or warnings can be returned in the ResponseHeader in the body of the response Serious issues can be returned as SOAP faults Workaround: to manually create a SOAP fault exception parameter: 1. Either create a data type in the SDM definitions package for SOAP fault information, or customize the ErrorInfo IDM data type. 2. Create a parameter on a ServiceInterface operation with the direction set to Out. 3. Set the parameter type to the SOAP fault data type you created in the SDM definitions package or to the ErrorInfo IDM data type. 4. Set the parameter as an exception parameter: In the Properties > Service view, select Exception, or In the Properties > Advanced view, set Is Exception to True. The exception parameter you created can be copied and pasted into other ServiceInterface operations as required The SDM generation utility fails when BOM capability operation parameter names have leading spaces. If the SDM generation utility encounters a BOM capability operation parameter whose name has leading spaces, it fails with this error message: Modification failed: "Create SDM Service from BOM Capability Operation" Workaround: delete leading spaces from BOM capability operation parameter names The BOM-to-IDM generation utility target tree cannot be updated if BOM has not been saved. If you create new classes in BOM, but do not save BOM and then run the BOM-to-IDM generation utility, the target tree will not update when you change the Select IDM Type to be Created option. When this happens, you cannot select a valid target element and therefore cannot click the Finish button in the wizard. Workaround: save BOM and rerun the BOM-to-IDM generation utility The BOM-to-IDM generation utility does not create component realizations for IDM classes. n/a When the BOM-to-IDM generation utility creates a class in IDM, it must also create a component realization from an IDM component to the class to specify which component the class belongs to. Workaround: manually create a component realization from the appropriate IDM component to the IDM class created by the BOM-to-IDM generation utility. Industry Models validation incorrectly reports problems when UML models are not open. When you validate BPS/IPS for Standard Tooling models or projects and all UML models are not open, validation errors or warnings can display indicating that intermodel mappings are missing. Workaround: ensure that all service models are open in the BPS/IPS for Standard Tooling project before you run Industry Models validation. 2

5 Known IBM Rational Software Architect issues and limitations Renaming RSA project breaks UML -> APM mappings. Renaming a project in RSA containing Business Process Model and Notation (BPMN) and UML models breaks mappings from the UML models to the BPMN models. The URL mappings are not updated when the project name changes. Workaround: do not rename BPS/IPS for Standard Tooling projects that contain BPMN models in RSA The BPMN 2.0 export of BPMN model that is linked to UML model can result in invalid XSD imports. The export to BPMN 2.0 can result in BPMN files that have invalid and missing XSD imports. Workaround: in RSA, validate the BPMN 2.0 files that are created by the export to BPMN 2.0 and manually fix the invalid XSD imports BPMN process diagrams have incorrect auto-layout. When BPMN process diagrams are opened and RSA applies its auto-layout logic: Some data flows appear outside the main diagram area. There is insufficient space between activities to see their details easily. Flow logic is not laid out properly, making it difficult to follow the flow path. Lane width can be too narrow for the number of elements that are contained in them. Workaround: manually lay out the BPMN process diagrams. You can also create layers to hide diagram elements for clarity. For example, you can create a layer that is named Data that contains all data objects, process data inputs and process data outputs. The data layer can then be shown or hidden Data types are not transformed to classes by the UML-to-Java transformation. The UML-to-Java transformation does not generate anything for UML data types. The UML-to-Java transformation must generate classes for data types. Workaround: this issue has been resolved in RSA v The export to BPMN 2.0 does not complete when the linked service model has interface generalizations. If a BPMN model has a service task linked to a UML interface operation, and the UML interface has a generalization to another interface, exporting the BPMN model to BPMN 2.0 will fail. Workaround: this issue has been resolved in RSA v Invalid WSDL and XSD files are generated when the "Support for XSD polymorphism and substitution groups" extension is enabled. When the com.ibm.xtools.transform.uml2.wsdl.globalelements UML-to-WSDL extension is enabled, generating WSDL and XSD files from the Industry Models service models results in thousands of validation errors. Workaround: this issue has been resolved in RSA v UML-to-WSDL transformation generates invalid WSDL elements for UML elements with spaces in their names. The UML-to-WSDL transformation generates invalid WSDL files for UML elements whose names contain spaces. Validating generated WSDL and XSD files in RSA results in validation errors such as: WSDL: The value 'Customer Relationship Management' of attribute 'name' must be of type ' WSDL: The 'testservice2' service name is not unique among all services. Workaround: manually fix the issues in the generated WSDL files. This issue has been resolved in RSA v

6 Duplicate BPMN connectors are created when you connect elements in the process diagram. In a BPMN process diagram, drawing a Connector between two elements can result in two connector lines in the diagram. Attempting to remove one of the duplicate connectors deletes both connectors from the diagram, and deletes the referenced BPMN element. Note: this is a display issue only. Duplicate BPMN elements are not created An invalid XSD file is created for enumerations from several source packages with the same name. If you select several packages (containing enumerations) with the same name in the source tree when you run the UML-to-XSD transformation, all enumerations are generated into a single XSD file, other empty XSD files are generated and XSD validation errors will display. Workaround: clear Customize the output according to the entries in the following table in the UMLto-XSD transformation configuration file UML-to-WSDL transformation results in circular XSD imports and unused XSD import validation warnings. XSD imports are now created for the derived types of directly referenced types in WSDL and XSD files that are created by the UML-to-WSDL transformation. This can result in: Validation warnings for unused XSD imports in the generated WSDL and XSD files Circular XSD imports within the XSD files, which can prevent the files from being imported into other tools. Workaround: manually remove unused XSD imports from the generated WSDL and XSD files. Known IBM Business Process Manager issues and limitations Some called processes are imported with incorrect start event logic. After import, for some called processes in APM, the start logic is imported incorrectly, where a parallel fork gateway is created into which flows one of the start events from the original BPMN2.0 model and out of which flows two sequence flows that are associated with the start event and the Invoked By Business Process flow that denotes this as a called process. Workaround: manually fix the start event logic The BPM Import is not handling item definitions as expected. In RSA, APM and OPM contain several item definitions that map to the same BOM class. When you export from RSA to BPMN 2.0 several item definitions are linked to the same XSD complextype. BPMN 2.0 item definitions do not have names, but the item definitions have tags to differentiate between them. When you import to BPM, rather than a business object for each BPMN 2.0 item definition with the name taken from the tag, a single business object is created for each XSD complextype. This results in the effective replacement of business objects by other business objects of the same underlying type during the import procedure. Workaround: if required, manually create the missing business objects (RFE) Auto-layout of BPMN process diagrams does not work correctly. Some imported BPMN processes are poorly laid out in Process Designer. For example: 1. Labels can overlap or obscure elements such as tasks 2. Connector Lines (sequence flows) can overlap elements such as gateways and tasks 3. Gateway connector lines are not optimal and can overlap Workaround: manually lay out the BPMN process diagrams. 4

7 n/a Import of large BPMN 2.0 model sets can fail. You may need to increase the maximum heap size of the BPM server in WebSphere Application Server before you import large Industry Models APM and OPM BPMN 2.0 model sets into BPM. If the heap size is not set large enough for large sets of BPMN2.0 model files, the import will fail. Workaround: Increase the maximum heap size of the BPM server in WebSphere Application Server. For example, set to 6 Gb on a 64 bit system. 5