The company adds a new mapping routine to the library and makes the updated library available to a number of the integration solutions.
The company begins processing payments on behalf of a business partner. The business partner's payments use a different data format and so a new map, MapPartnerPaymentProcessingToCanonical.map is added to the MessageMappingLib library. The Message Broker projects and the App1 application are all expected to process the business partner's payments. However, the App2 application is not connected to the business partner system and so there is no urgency to make the updated library available to the App2 application. The library is updated and redeployed so that the updated resources are available to only the Proj1 and Proj2 Message Broker projects and the App1 application.
The following screen capture shows the resulting development environment when the library is updated with a new message map and associated resources. Because both of the applications contain a reference to the library, the new map is shown in the library references for the development resources of both applications.
The following screen capture shows the runtime environment after the updated library and the App1 application are deployed to the execution group. You can see that the updated library is available to the two Message Broker projects and to the App1 application. However, because the App2 application has not been redeployed, the App2 application is still using the original version of the library.