The present invention proposes a method for providing a broadcast content in an apparatus, the method comprising: requesting a filter code to an application running on the apparatus by using a first Application Programming Interface (API); receiving a JavaScript Object Notation (JSON) object from the application in response to the first API; storing the filter code; receiving an Extended File Delivery Table (EFDT) having a first filter code associated with a first file; and selectively downloading the first file by comparing the stored filter code with the first filter code in the EFDT.

Aspects of the present disclosure involve systems, methods, devices, and the like for creating an application lifecycle management platform for big data applications. In one embodiment the lifecycle management platform can include a multiple-layer container file that integrates multiple big-data tools/platforms. The system may create a generic template application, create a build environment for the generic template application, create a test environment for the generic template application, and run the built generic template application in the test environment prior to the user writing any new code in the generic template application. In one embodiment, the test environment includes a container management system or virtual machine that launches the big data application (which may be the generic template application before a developer edits the file) on a separate big-data server cluster.

The present invention provides a technology for invoking a non-periodic-execution function module from a periodic-execution control program. A control system that comprises first and second control parts (C1, C2) and a storage device that stores control programs (210, 211) for a controller. The control programs (210, 211) include a periodic-execution function module (55B) that invokes a non-periodic-execution function module (55A). The first control part (C1) reflects the value of an input variable for the periodic-execution function module (55B) in an argument for the non-periodic-execution function module (55A) and outputs an execution start command for the function modules to the second control part (C2). The second control part (C2) outputs a return value for the non-periodic-execution function module (55A) to the first control part (C1). The first control part (C1) reflects the return value in an output variable for the periodic-execution function module (55B).

A system, product and process for building a package dependencies data structure. The method comprises determining a package instance identifier of the package to be processed. The package instance identifier is determined based on a unique identifier of the package to be processed and based on a unique identifier of a dependency sub-tree of the package to be processed in the package instance identifier. The package instance identifier is utilized to determine if a node representing the package to be processed exists or not. In case the node does not exist already in the data structure, the node is created and added.

A system, product and process for building a package dependencies data structure. The method comprises determining a package instance identifier of the package to be processed. The package instance identifier is determined based on a unique identifier of the package to be processed and based on a unique identifier of a dependency sub-tree of the package to be processed in the package instance identifier. The package instance identifier is utilized to determine if a node representing the package to be processed exists or not. In case the node does not exist already in the data structure, the node is created and added.

The present invention provides a deployment platform that enables solution modules to be created and deployed without writing new code. The solution modules may include existing solutions, solution components, connectors, and the like selected from a solution library. The deployment platform includes a development engine providing functionality for generating deployment information for the solution module. The deployment information may include a blueprint or other information for deploying the solution module to target infrastructure. The deployment platform also includes a deployment engine providing functionality for deploying the solution module to the target infrastructure automatically. During deployment, the deployment engine pushes components of the solution module to the target infrastructure in accordance with the deployment information. During and after deployment, information may be captured and recorded to a distributed ledger to provide end-to-end visibility into the deployed solution over the deployment lifecycle (e.g., including initial deployment, updates/upgrades, and decommissioning).

A method may include receiving a first definition of an object type from a first software component and a second definition of the object type from a second software component. The object type may be labeled by an ID. The method may further include storing, in a dynamic graph, a node labeled by the ID, and storing, in a type definition repository external to the dynamic graph, the first definition of the object type and the second definition of the object type. The method may further include receiving, from the first software component, a modified first definition of the object type. The method may further include replacing, in the type definition repository and using the ID, the first definition of the object type with the modified first definition, and transmitting, to the second software component, a message indicating a need to lookup, by the ID, the modified first definition.

A method may include receiving a first definition of an object type from a first software component and a second definition of the object type from a second software component. The object type may be labeled by an ID. The method may further include storing, in a dynamic graph, a node labeled by the ID, and storing, in a type definition repository external to the dynamic graph, the first definition of the object type and the second definition of the object type. The method may further include receiving, from the first software component, a modified first definition of the object type. The method may further include replacing, in the type definition repository and using the ID, the first definition of the object type with the modified first definition, and transmitting, to the second software component, a message indicating a need to lookup, by the ID, the modified first definition.

Source code routines are generated for storage management in a storage code development management tool. A script that includes the source code routines is generated. The storage code development management tool receives indications based on an execution of an object code generated via execution of the script. The storage code development management tool modifies the source code routines based on the received indications.

Disclosed are various embodiments for anti-pattern detection in extraction and deployment of a microservice. A software modernization service is executed to analyze a computing application to identify various applications. When one or more of the application components are specified to be extracted as an independently deployable subunit, anti-patterns associated with deployment of the independently deployable subunit are determined prior to extraction. Anti-patterns may include increases in execution time, bandwidth, network latency, central processing unit (CPU) usage, and memory usage among other anti-patterns. The independently deployable subunit is selectively deployed separate from the computing application based on the identified anti-patterns.