Claims:WE CLAIM:
1. A method for migrating automation assets in an enterprise system, the method comprising:
receiving, by an asset management system 100, an input data associated with the automation assets from a source application 102;
configuring, by the asset management system 100, a first set of data types associated with the input data, by identifying a corresponding data type from a second set of data types, configured in a target application 104;
generating, by asset management system 100, a relationship between each of a plurality of entities associated with the first set of data types and a corresponding plurality of entities associated with the second set of data types in the target application 104; and
migrating, by asset management system 100, the plurality of entities associated with the first set of data types from the source application 102 to the target application 104 based on the generated relationship.
2. The method as claimed in claim 1, wherein the input data comprises at least one of a plurality of scripts 212, a plurality of libraries 214, a plurality of objects 216, a plurality of functions 218 and a plurality of data files 220.
3. The method as claimed in claim 1, wherein each of the first set of data types is at least one of object type 222, argument 224, data file 220 and execution settings 226.
4. The method as claimed in claim 1, wherein each of the second set of data types is at least one of object type 222, argument 224, data file 220 and execution settings 226.
5. The method as claimed in claim 1, wherein configuring the first set of data types associated with the input data comprises:
obtaining at least one of the first set of data types associated with the input data from the source application 102 and data associated with the target application 104, based on details received by a user;
identifying the second set of data types, from the data associated with the target application 104, corresponding to the first set of data types; and
storing the at least one of first set of data types associated with the input data and identified second set of data types in a storage unit, based on location identified by the user.
6. The method as claimed in claim 1, wherein each of the plurality of entities is one of a property 228 and an argument 224, associated with one of the first set of data types and second set of data types.
7. The method as claimed in claim 1, wherein generating the relationship between each of a plurality of entities associated with the first set of data types and a corresponding plurality of entities associated with the second set of data types, comprises:
identifying an entity type for each of the first set of data types associated with the input data; and
mapping each of the identified entity type of the first set of data types with an entity type of the second set of data types, wherein the entity type is identified for each of the second set of data types associated with the target application 104, thereby generating the relationship.
8. The method as claimed in claim 1, wherein migrating the plurality of entities from the source application 102 to the target application 104 comprises:
obtaining the first set of data types and the second set of data types from the source application 102 and the target application 104 respectively;
obtaining an entity type for each of the first set of data types;
obtaining the relationship between each of the obtained entity type with a corresponding entity type of the second set of data types; and
migrating values associated with each of the entity type associated with the first set of data types to the corresponding entity type associated with the second set of data types.
9. The method as claimed in claim 8, wherein migrating the plurality of entities from the source application 102 to the target application 104 further comprises:
identifying non-establishment of a relationship for an entity type, associated with the first set of data types with a corresponding entity type associated with the second set of data types;
mapping the entity type, associated with the first set of data types, with a corresponding entity type being identified from the second set of data types thus obtained;
establishing a relationship between the entity type, associated with the first set of data types, with the corresponding entity type identified from the second set of data types thus obtained; and
storing the established relationship in a storage unit 108 of the asset management system 100.
10. The method as claimed in claim 1 further comprises:
uploading the migrated plurality of entities associated with the first set of data types from the source application 102 to the target application 104; and
validating the first set of data types by executing at least one of a plurality of scripts 212 associated with the first set of data types.
11. An asset management system 100 for migrating automation assets in an enterprise system, the asset management system 100 comprising:
a processor 204; and
a memory 206, communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, causes the processor 204 to:
receive an input data associated with the automation assets from a source application 102;
configure a first set of data types associated with the input data, by identifying a corresponding data type from a second set of data types, configured in a target application 104;
generate a relationship between each of a plurality of entities associated with the first set of data types and a corresponding plurality of entities associated with the second set of data types in the target application 104; and
migrate the plurality of entities associated with the first set of data types from the source application 102 to the target application 104 based on the generated relationship.
12. The system as claimed in claim 11, wherein the input data comprises at least one of a plurality of scripts 212, a plurality of libraries 214, a plurality of objects 216, a plurality of functions 218 and a plurality of data files 220.
13. The system as claimed in claim 11, wherein each of the first set of data types is at least one of object type 222, argument 224, data file 220 and execution settings 226.
14. The system as claimed in claim 11, wherein each of the second set of data types is at least one of object type 222, argument 224, data file 220 and execution settings 226.
15. The system as claimed in claim 11, wherein to configure the first set of data types associated with the input data, the instructions causes the processor 204 to:
obtain at least one of the first set of data types associated with the input data from the source application 102 and data associated with the target application 104, based on details received by a user;
identify the second set of data types, from the data associated with the target application 104, corresponding to the first set of data types; and
store the at least one of first set of data types associated with the input data and identified second set of data types in a storage unit, based on location identified by the user.
16. The system as claimed in claim 11, wherein each of the plurality of entities is one of a property 228 and an argument 224, associated with one of the first set of data types and second set of data types.
17. The system as claimed in claim 11, wherein to generate the relationship between each of a plurality of entities associated with the first set of data types and a corresponding plurality of entities associated with the second set of data types, the instructions causes the processor 204 to:
identify an entity type for each of the first set of data types associated with the input data; and
map each of the identified entity type of the first set of data types with an entity type of the second set of data types, wherein the entity type is identified for each of the second set of data types associated with the target application, thereby generating the relationship.
18. The system as claimed in claim 11, wherein to migrate the plurality of entities from the source application 102 to the target application 104, the instructions causes the processor 204 to:
obtain the first set of data types and the second set of data types from the source application 102 and the target application 104 respectively;
obtain an entity type for each of the first set of data types;
obtain the relationship between each of the obtained entity type with a corresponding entity type of the second set of data types; and
migrate values associated with each of the entity type associated with the first set of data types to the corresponding entity type associated with the second set of data types.
19. The system as claimed in claim 18, wherein to migrate the plurality of entities from the source application 102 to the target application 104, the instructions causes the processor 204 to:
identify non-establishment of a relationship for an entity type, associated with the first set of data types with a corresponding entity type associated with the second set of data types;
map the entity type, associated with the first set of data types, with a corresponding entity type being identified from the second set of data types thus obtained;
establish a relationship between the entity type, associated with the first set of data types, with the corresponding entity type identified from the second set of data types thus obtained; and
store the established relationship in a storage unit 108 of the asset management system 100.

20. The system as claimed in claim 11, wherein the instructions further causes the processor 204 to:
upload the migrated plurality of entities associated with the first set of data types from the source application 102 to the target application 104; and
validate the first set of data types by executing at least one of a plurality of scripts 212 associated with the first set of data types.

Dated this 14th day of March, 2017

SRAVAN KUMAR GAMPA
IN/PA-1744
OF K & S PARTNERS
AGENT FOR THE APPLICANT
, Description:
TECHNICAL FIELD
The present subject matter is related, in general to an enterprise system, and more particularly, but not exclusively to a method and a system for migrating automation assets in an enterprise system.