Device based automated tool integration for lifecycle management platform

Patent metadata

Field	Value
Publication number	US-10353755-B2
Application number	US-201715482379-A
Country	US
Kind code	B2
Filing date	Apr 7, 2017
Priority date	Apr 12, 2016
Publication date	Jul 16, 2019
Grant date	Jul 16, 2019

Abstract

A device may identify a tool operating on a first device for integration into a lifecycle management platform operating on a second device. The tool may be associated with providing a functionality not included in the lifecycle management platform. The first device may be external to the second device. The device may determine a set of tool attributes for data events associated with the tool. The data events may include a data input, a data output, a new message, an updated message, a deleted message, or the like. The device may select a message format based on the set of tool attributes. The device may configure adaptation for a tool application programming interface (API) of the tool and a platform API of the lifecycle management platform based on the message format. The device may provide information associated with configuring adaptation for the tool API and the platform API.

First claim

What is claimed is:

1. A device, comprising:
one or more processors to:
identify a tool operating on a first device for integration into a lifecycle management platform operating on a second device,
the tool being associated with providing a functionality not included in the lifecycle management platform,
the first device being external to the second device;

determine a set of tool attributes for data events associated with the tool,
the data events including at least one of:
a data input,
a data output,
a new message,
an updated message, or
a deleted message;

select a message format based on the set of tool attributes;
configure adaptation for a tool application programming interface (API) of the tool and a platform API of the lifecycle management platform based on the message format; and
provide information associated with configuring adaptation for the tool API and the platform API.

2. The device of claim 1 , where the one or more processors, when providing the information associated with configuring adaptation, are to:
store a tool adapter for the tool based on configuring adaptation for the tool API and the platform API,
the tool adapter including a set of adaptation rules associated with converting messages between a first format associated with the tool and a second format associated with the lifecycle management platform.

3. The device of claim 1 , where the one or more processors are further to:
receive a message for adaptation;
perform message verification for the message based on receiving the message;
perform message adaptation using the information associated with configuring adaptation for the tool API and the platform API to generate an adapted message; and
output the adapted message based on generating the adapted message.

4. The device of claim 3 , where the one or more processors, when performing message adaptation, are to:
perform an API call associated with the tool API or the platform API to cause the message to be provided to the tool or the lifecycle management platform.

5. The device of claim 3 , where the one or more processors, when performing message adaptation, are to:
generate a message object in a particular format,
the particular format being different from a format of the message at a time when the message was received; and

where the one or more processors, when outputting the adapted message, are to:
output the message object.

6. The device of claim 1 , where the one or more processors, when determining the set of tool attributes, are to:
identify a first set of permitted values associated with a tool attribute of the set of tool attributes,
the first set of permitted values being different from a second set of permitted values associated with a corresponding lifecycle management platform attribute of a set of lifecycle management platform attributes; and

where the one or more processors, when configuring adaptation for the tool API and the platform API, are to:
generate a set of rules for converting between the first set of permitted values and the second set of permitted values.

7. The device of claim 1 , where the one or more processors, when determining the set of tool attributes, are to:
identify a first header format associated with the tool,
the first header format being different from a second header format associated with the lifecycle management platform; and

where the one or more processors, when configuring adaptation for the tool API and the platform API, are to:
generate a set of rules for converting between the first header format and the second header format,
the set of rules including one or more rules for rearranging an ordering of data elements of the first header format into an ordering associated with the second header format.

8. The device of claim 1 , where the one or more processors are further to:
receive a message in a canonical data format associated with the lifecycle management platform;
determine that the message is from a trusted source; and
bypass tool adaptation for the message to provide the message to the lifecycle management based on determining that the message, in the canonical data format, is from the trusted source.

9. The device of claim 1 , where the one or more processors are further to:
receive a message in a canonical data format associated with the lifecycle management platform;
determine that the message is from an untrusted source; and
perform tool adaptation for the message to provide the message to the lifecycle management based on determining that the message, in the canonical data format, is from the untrusted source.

10. A method, comprising:
receiving, by a device, a message for adaptation between a first format associated with a tool operating on a first device and a second format associated with a lifecycle management platform operating on a second device,
the lifecycle management platform including a set of functionalities associated with managing resources for a development project,
the tool including a functionality associated with managing resources for the development project that is not included in the set of functionalities;

identifying, by the device, a tool adapter including a set of rules for adapting messages between the first format and the second format,
the tool adapter being stored in an archive of tool adapters;

determining, by the device, whether the message is from a trusted or untrusted source;
selectively performing, by the device, adaptation of the message between the first format and the second format using the set of rules included in the tool adapter to generate an adapted message based on a result of determining whether the message is from a trusted or untrusted source,
the message being adapted when from the untrusted source,
the message being bypassed from adaptation when from the trusted source; and

outputting, by the device, the adapted message.

11. The method of claim 10 , where receiving the message comprises:
communicating with the first device to receive the message in the first format,
the first format being a RAW format that is associated with the tool; and where outputting the adapted message comprises:
communicating with the second device to provide the adapted message in a canonical data model format associated with the lifecycle management platform.

12. The method of claim 10 , where receiving the message comprises:
communicating with the second device to receive the message in the second format,
the second format being a canonical data model format associated with the lifecycle management platform; and
where outputting the adapted message comprises:
communicating with the first device to provide the adapted message in a RAW format that is associated with the tool.

13. The method of claim 10 , where outputting the adapted message comprises:
performing an application programming interface (API) call to cause a data event associated with the message.

14. The method of claim 10 , further comprising:
identifying the tool,
determining a set of tool attributes for data events associated with the tool,
the data events including at least one of:
a data input,
a data output,
a new message,
an updated message, or
a deleted message;

configuring adaptation for a tool application programming interface (API) of the tool and a platform API of the lifecycle management platform based on the set of tool attributes; and
storing the tool adapter in the archive of tool adapters based on configuring adaptation for the tool API and the platform API,
the tool adapter storing information associated wi

Assignees

• Accenture Global Solutions Ltd

Inventors

• Srivastava Krupa
• Koushik Vijayaraghavan
• Deshpande Chandrashekhar
• Lazarus Mark
• Dang Le G
• Desai Madhusudhana
• Kute Sumit
• Shukla Arpan
• Jamir Tiarenla
• Sawant Prashant
• Sharma Rohan
• Ghosh Bhaskar
• SEKHAR Mohan
• Prasad Rajendra T

Classifications

• G06F8/70

  Software maintenance or management · CPC title

• G06F8/36

  Software reuse · CPC title

• G06F9/45533 Primary

  Hypervisors; Virtual machine monitors · CPC title

• G06F9/45504

  Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators · CPC title

• G06F9/545 Primary

  where tasks reside in different layers, e.g. user- and kernel-space · CPC title