Technique for transforming a standard messaging component to a customized component

1. A method comprising:

receiving selection of a component at a porting module;

retrieving a source code for the selected component and a component configuration file for the selected component;

receiving component data associated with the component;

generating metadata associated with the received component based on the received component data, wherein generating metadata further comprises:

identifying at least one attribute for an endpoint of the selected component;

extracting the at least one identified attribute; and

generating a user interface (UI) metadata file and a metadata configuration file with the extracted at least one identified attribute;

modifying the component configuration file of the selected component to generate a modified configuration file;

generating an integration adapted by modifying the retrieved source code for the selected component with the generated metadata and the modified configuration file; and

deploying the integration adapter.

2. The method of claim 1 , further comprising:

injecting a custom bean in the transformed source code.

3. The method of claim 1 , further comprising:

validating the generated integration adapter.

4. The method of claim 1 , further comprising:

generating a design time integration flow using the deployed integration adapter.

5. The method of claim 4 , further comprising:

executing the design time integration flow.

6. The method of claim 1 , wherein the component configuration file is an XML file.

7. The method of claim 6 , wherein modifying the component configuration file of the selected component further comprises:

embedding one or more transitive dependencies in the modified configuration file;

adding a validation element to the configuration file; and

removing a parent element from the configuration file.

8. The method of claim 1 , wherein the at least one attribute is at least one of a component scheme, a Uniform Resource Identifier (URI), sender endpoint parameter, receiver endpoint parameter, component name, component vendor, component version.

9. A system of comprising:

a target endpoint;

a component providing a uniform endpoint interface to the target endpoint;

a porting module;

a porting processor in communication with the porting module and operative to execute processor-executable process steps to cause the system to:

receive selection of the component;

retrieve a source code for the selected component and a component configuration file for the selected component;

receive component data associated with the component;

generate metadata associated with the received component based on the received component data, wherein generating metadata further comprises process steps to cause the system to:

identify at least one attribute for an endpoint of the selected component;

extract the at least one identified attribute; and

generate a User Interface (UI) metadata file and a metadata configuration file with the extracted at least one identified attribute;

modify the component configuration file of the selected component to generate a modified configuration file;

generate an integration adapter by modifying the retrieved source code for the selected component with the generated metadata and the modified configuration file;

validate the generated integration; and

deploy the integration adapter.

10. The system of claim 9 , further comprising process steps to cause the system to:

inject a custom bean in the transformed source code.

11. The system of claim 9 , further comprising process steps to cause the system to:

generate a design time integration flow using the deployed integration adapter; and

execute the design time integration flow.

12. The system of claim 9 , wherein the component configuration file is an XML, file.

13. The system of claim 12 , wherein modifying the component configuration file of the selected component further comprises process steps to cause the system to:

embed one or more transitive dependencies in the modified configuration file;

add a validation element to the configuration file; and

remove a parent element from the configuration file.

14. The system of claim 9 , wherein the at least one attribute is at least one of a component scheme, a Uniform Resource Identifier (URI), sender endpoint parameter, receiver endpoint parameter, component name, component vendor, component version.

15. A non-transitory computer-readable medium storing program instructions executed by a processor of a computer system having memory, the medium comprising instructions for causing the processor to perform:

receiving selection of a component at a porting module;

retrieving a source code for the selected component and a component configuration file for the selected component;

receiving component data associated with the component;

generating metadata associated with the received component based on the received component data, wherein generating metadata further comprises instructions to cause the processor to perform:

identifying at least one attribute for an endpoint of the selected component;

extracting the at least one identified attribute; and

generating a User Interface (UI) metadata file and a metadata configuration file with the extracted at least one identified attribute;

modifying the component configuration file of the selected component to generate a modified configuration file;

generating an integration adapter by modifying the retrieved source code for the selected component with the generated metadata and the modified configuration file; and

deploying the integration adapter.

16. The medium of claim 15 , wherein modifying the component configuration file of the selected component further comprises instructions to cause the processor to perform:

embedding one or more transitive dependencies in the modified configuration file;

adding a validation element to the configuration file; and

removing a parent element from the configuration file.

17. The medium of claim 15 , wherein the at least one attribute is at least one of a component scheme, a Uniform Resource Identifier (URI), sender endpoint parameter, receiver endpoint parameter, component name, component vendor, component version.