Network tool synchronization

Abstract

In one implementation, a system for network tool synchronization includes a methodology engine to receive a data methodology of an enterprise architecture tool from the enterprise architecture tool. In addition, the system includes a functionality engine to analyze deployment diagrams of an orchestration tool to determine a functionality of the orchestration tool. In addition, the system includes an architecture engine to select information from the enterprise architecture tool based on the functionality of the orchestration tool. In addition, the system includes an information engine to export the selected information to the orchestration tool.

What is claimed is: 
     
       1. A system for network tool synchronization, comprising:
 a processor; 
 a non-transitory storage medium storing synchronization instructions executable on the processor to:
 receive a data methodology of an enterprise architecture tool from the enterprise architecture tool, the data methodology specifying at least one business function of an entity, a plurality of applications for performing the at least one business function, and a plurality of hardware components that implement the plurality of applications; 
 determine, using a catalog of an orchestration tool that deploys and manages applications providing respective services of a transaction, a functionality of the orchestration tool, the catalog of the orchestration tool separate from the data methodology of the enterprise architecture tool; 
 select, based on the determined functionality of the orchestration tool, information of the data methodology received from the enterprise architecture tool, the selected information relevant to applications and hardware components used by the orchestration tool to implement the functionality, and the selected information not included in the catalog of the orchestration tool; and 
 export the elected information to the orchestration tool to cause update of the catalog of the orchestration tool. 
 
 
     
     
       2. The system of  claim 1 , wherein the data methodology is a tree like representation that represents relationships between features of the system, the features comprising the at least one business function, the plurality of applications, and the plurality of hardware components. 
     
     
       3. The system of  claim 2 , wherein the tree like representation includes a plurality of levels including a first level relating to transactions, a second level relating to applications, and a third level relating to hardware components. 
     
     
       4. The system of  claim 1 , wherein the catalog contains information from different users. 
     
     
       5. The system of  claim 1 , wherein the synchronization instructions are executable on the processor to cause replacement of existing information within the catalog of the orchestration tool with the exported data. 
     
     
       6. The system of  claim 1 , wherein the exporting does not export, to the orchestration tool, information of the data methodology not relevant to the functionality of the orchestration tool. 
     
     
       7. The system of  claim 1 , wherein the data methodology represents relationships among the at least one business function, the plurality of applications, and the plurality of hardware components. 
     
     
       8. A non-transitory computer readable medium storing instructions that upon execution cause a system to:
 receive a data methodology of an enterprise architecture tool, the data methodology specifying, for the system, a structural representation of at least one business function of an entity, a plurality of applications for performing the at least one business function, and a plurality of hardware components that implement the plurality of applications; 
 determine, using a catalog of an orchestration tool that deploys and manages applications providing respective services of a transaction, a functionality of the orchestration tool, the catalog of the orchestration tool separate from the data methodology of the enterprise architecture tool; 
 identify, from the enterprise architecture tool and based on the determined functionality of the orchestration tool, data of the data methodology relevant to the plurality of applications managed by the orchestration tool, and the plurality of hardware components managed by the orchestration tool, the identified data specifying information not included in the catalog of the orchestration tool; and 
 export the identified data to the orchestration tool to cause update of the catalog of the orchestration tool. 
 
     
     
       9. The non-transitory computer readable medium of  claim 8 , wherein the instructions upon execution cause the system to receive application information from the orchestration tool, and export the received application information to the enterprise architecture tool. 
     
     
       10. The non-transitory computer readable medium of  claim 9 , wherein the application information includes geographical locations of hardware, network functionality, and security of the system. 
     
     
       11. The non-transitory computer readable medium of  claim 9 , wherein the instructions to export the received application information includes instructions to export the received application information to corresponding locations of the data methodology. 
     
     
       12. The non-transitory computer readable medium of  claim 8 , wherein the exported data replaces existing information within the catalog of the orchestration tool. 
     
     
       13. The non-transitory computer readable medium of  claim 8 , wherein the data methodology is a tree like representation that represents each business function on a first level, each application on a second level, and each hardware component on a third level. 
     
     
       14. The non-transitory computer readable medium of  claim 8 , wherein the data methodology represents relationships among the at least one business function, the plurality of applications, and the plurality of hardware components. 
     
     
       15. The non-transitory computer readable medium of  claim 8 , wherein the exporting does not export, to the orchestration tool, data of the data methodology not relevant to the functionality of the orchestration tool. 
     
     
       16. A method for network tool synchronization, comprising:
 receiving, by a system comprising a processor, a data methodology of an enterprise architecture tool, wherein the data methodology is a representation of multi-tier information specifying at least one business function of an entity, a plurality of applications for performing the at least one business function, and a plurality of hardware components that implement the plurality of applications; 
 determining, by the system using a catalog of an orchestration tool that deploys and manages applications providing respective services of a transaction, a functionality of the orchestration tool, the catalog of the orchestration tool separate from the data methodology of the enterprise architecture tool; 
 selecting, by the system using the catalog of the orchestration tool used to perform the at least one business function, information of the data methodology, the selected information relevant to applications and hardware components used by the orchestration tool to implement the functionality, and the selected information not included in the catalog of the orchestration tool; and 
 exporting, by the system, the selected information to the orchestration tool to cause update of the catalog of the orchestration tool. 
 
     
     
       17. The method of  claim 16 , wherein the data methodology includes a representation of information based on a business architecture. 
     
     
       18. The method of  claim 16 , wherein exporting the selected information to the orchestration tool causes replacing existing information within the catalog of the orchestration tool with the selected information. 
     
     
       19. The method of  claim 16 , wherein the data methodology is a tree like representation that represents each business function on a first level, each application on a second level, and each hardware component on a third level. 
     
     
       20. The method of  claim 16 , wherein the exporting does not export, to the orchestration tool, information of the data methodology not relevant to the functionality of the orchestration tool. 
     
     
       21. The method of  claim 16 , wherein the data methodology represents relationships among the at least one business function, the plurality of applications, and the plurality of hardware components.