How do BRMSs fit into standard IT platforms like Java, .NET and COBOL?
The ease of integration depends on the BRMS. When a BRMS is natively built in the platform of your business, the design, maintenance and execution of BRMS applications are simplified. From a developer’s standpoint, a BRMS should fit within the most frequently used development environment. For example, a BRMS used with Java stacks should fit within the Eclipse Integrated Development Environment (IDE); a BRMS should work with Microsoft Visual Studio and the Microsoft SharePoint collaboration infrastructure when used on the .NET platform. COBOL is an interesting case: A BRMS system with COBOL deployment capabilities will resolve both the need for speed and the protection of previous investments, allowing the externalization of business logic from legacy COBOL systems for better and faster change management, while ensuring the continued business operations of core support systems.
The ease of integration depends on the BRMS. When a BRMS is natively built in the platform of your business, the design, maintenance and execution of BRMS applications are simplified. From a developer’s standpoint, a BRMS should fit within the most frequently used development environment. For example, a BRMS used with Java stacks should fit within the Eclipse Integrated Development Environment (IDE); a BRMS should work with Microsoft Visual Studio and the Microsoft SharePoint collaboration infrastructure when used on the .NET platform. COBOL is an interesting case: A BRMS system with COBOL deployment capabilities will resolve both the need for speed and the protection of previous investments, allowing the externalization of business logic from legacy COBOL systems for better and faster change management, while ensuring the continued business operations of core support systems.
