FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See Section 10 and Rule 13)
Title of invention:
SYSTEM AND METHOD FOR AUTOMATED SERVICE DEPLOYMENT
Applicant
TATA Consultancy Services Limited A company Incorporated in India under The Companies Act, 1956
Having address:
Nirmal Building, 9th Floor,
Nariman Point, Mumbai 400021,
Maharashtra, India
The following specification particularly describes the invention and the manner in which it is to be performed.

FIELD OF THE INVENTION:
The present invention generally relates to a field of service deployment over Enterprise Service Bus (ESB) in a Service Oriented Architecture (SOA) platform. More particularly, the invention relates to a system and method for providing automation and assurance in services deployment irrespective of host environment.
BACKGROUND OF THE INVENTION:
Service oriented architecture (SOA) is an architectural paradigm for development of software applications. An Enterprise Service Bus (ESB) is an underlying infrastructure for the SOA. ESB plays an important role where several services or applications compiled in different technologies or languages are to be deployed and used on a common platform. ESB acts as a middleware or a communication channel between these different technologies from where these services are made widely available. Different tasks.-are.performed on the ESB platform that includes transformation i.e., mapping of one data format onto another in order to ensure the inter-operability among the various systems coupled with the ESB platform, routing of the messages from one component to another and maintaining communication by delivering the messages among the organizations.
Deploying the services or the applications on the ESB platform is a complex task as it requires lifting of code from one environment to another. During such deployment process, settings of static as well as dynamic configurations need to be considered. During this process, chances of deployment failure are high because of an interdependency of the tasks among themselves. Moreover, new environment settings are crucial from service compatibility perspective, hence, though a service may be successfully deployed, there are high changes of failure of its execution due to compatibility issues with the host environment.
Therefore, to fine tune these considerations for service deployment, a substantial business hours are consumed, leading to wastage of effort and time. Thus, an errorless

and flawless deployment of the services or applications for desired quality of performance is not substantially addressed in the art of the invention.
Moreover, monitoring deployment and performance verification of the deployed services for desired performance may not be possible with the existing practice of service deployment that follows to formalize an application and execute at the pre-identified nodes. Accordingly, for each execution both primary and secondary nodes are required to be identified a priory, and upon identification it requires execution at each individual nodes which involves execution of repetitive steps performed even at insignificant nodes. Accordingly, considering such repetitive nature of the execution steps at irrelevant nodes, a more simple and user friendly execution method is required that would avoid repetitions and offer user a minimum effort for seamless deployment of services across the network.
Detecting latencies in message transfer, response time and determining node-performance in the network are still looked upon as a separate task and generally extra efforts and time is spent towards it as one of the activities of troubleshooting. Accordingly, a comprehensive deployment solution is required which not only deploy services across the network but also monitor deployment progress and subsequent performance validation thereof.
OBJECTS OF THE INVENTION
The primary objective of a present invention is to provide a system and a method to deploy services across nodes with minimum human intervention.
Another object of the invention is to provide a system and a method that enables automatic execution of service deployment with a single click action.
Another object of the present invention is to provide an adaptive system and a method to deploy services in accordance with changes in any static or dynamic configurations of network and business processes.

Yet another object of the present invention is to provide a system and a method that enables errorless and flawless deployment of services by devising an integrated deployment having monitored deployment followed by validation of the nodes for service requests.
Yet another object of the present invention is to provide a system and a method that enables concurrent deployment of services on one or more nodes using deployment scripts.
Still another object of the present invention is to provide a computer-implemented system having one or more processor executable modules for achieving at least one of the aforesaid objects of the present invention.
SUMMARY OF THE INVENTION
Before the present system-and method, enablement are described, it is to-be understood that this application is not limited to the particular system, and methodologies described, as there can be multiple possible embodiments which are not expressly illustrated in the present disclosure. It is also to be understood that the terminology used in the description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present invention.
The present invention introduces a computer-implemented system and a computer-implemented method for enabling automation in environment independent deploying and monitoring of ESB services. The present invention further facilitates the concurrent deployment execution of the services on a plurality of node using deployment scripts. The system configures an automated build from a source control repository for bundling required artifacts as an installable unit. The bundled artifacts and base binding files are configured within an installer package file which is used to deploy the services. The present invention executes the deployment process with a single click action, wherein said single click action triggers the execution of plurality

of cascaded tasks in a predetermined sequence. The cascaded tasks comprises of sequenced steps which are executed by corresponding deployment scripts irrespective of node. During deployment of the services, the user is sequentially prompted for each error or discrepancies. Further, the present invention is configured to provide side-by-side monitoring of the deployment progress and maintains a log at each stage of the deployment. The present invention also facilitates the user to incorporate on the fly changes within the static and dynamic configuration settings of the services during deployment. The process of binding the environment specific parameter's are accomplished at the point of deployment based on a central configuration store. This central configuration store maintains all the environment specific key value pair for different environments. Upon deployment of the services, the system verifies each service end point in the plurality of nodes. The verification is accomplished with the help of a batch file which triggers the command to check if the services are up and - running. Further it will trigger specific set-of-insttuetion to verify the operations under each service with the help of a predefined sample payload. If there is an exception in the response message then it will be logged as a failure with exception details. Otherwise it will be logged as success.
BRIEF DESCRIPTION OF THE DRAWINGS
The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings various stages of the invention; however, the invention is not limited to the specific apparatus and method disclosed in the drawings.
Figure 1 is the block diagram of the system (100) illustrating the multiple embodiments of the present invention.
Figure 2 is the flow diagram (200) illustrating the automated ESB service deployment and monitoring according to one aspect of the present invention.

DETAILED DESCRIPTION OF THE INVENTION
The invention will now be described with respect to various embodiments. The following description provides specific details for understanding of, and enabling description for, these embodiments of the invention. The words "comprising," "having," "containing," and "including," and other forms thereof, are intended to be equivalent in meaning and be open ended in that an item or items following any one of these words is not meant to be an exhaustive listing of such item or items, or meant to be limited to only the listed item or items.
It will be readily understood that the components of the present invention, as generally described and illustrated in the Figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments of the invention, as represented in the -Figures-and-flowcharts, is not intended to limit the scope-of the incention as claimed, but is merely representative of certain examples of presently contemplated embodiments in accordance with the invention.
The presently described embodiments will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. Moreover, flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
The present invention generally provides a computer-implemented system and a computer-implemented method for concurrently deploying and monitoring services across a plurality of nodes connected to ESB with minimum human intervention.

For a given business architecture, generally nodes are connected to ESB in a predefined configuration and are configured to follow predefined communication protocols. User, in the present invention is required to identify the installation scripts and input destination nodes to which service deployment is intended. Once started, the further part of deployment and nodes/service validation runs in an unattended mode.
To create an installation script, the services are bundled having the required artifacts. Such bundled services are deployed concurrently at a primary and secondary nodes and each deployment stage is monitored for errors and discrepancies. Monitoring during the deployment involves concurrent logs maintenance for each stage of the deployment. Upon deployment, the services are verified at each service end point in the plurality of nodes.
In an embodiment-of-the-invention, the deployment tool includes the-assemblies the base configuration file with XML pre processing instructions, the configuration store repository, the powershell/Ant deployment scripts, the deployment logs generated during the time of deploy, the verification script for both technical/functional verification of deployment.
During each deployment execution, a service code is initially installed on the each primary node and subsequently replicated on the corresponding secondary nodes thereof by using replication logic. In a highly available environment there will be multiple nodes behind a load balancer capable of handling concurrent request. One of the nodes will be treated as a primary node and the others as secondary nodes. During a deploy processes, the assemblies will be deployed in all the nodes which include both primary and secondary. This is accomplished by executing the same set of scripts in all the environments.
In another embodiment of the invention said deployment tool comprises of various processor-executable modules. Each said processor-executable module performs a particular set of task upon execution of the processor. One of the modules of said

system is a build configuration module which configures an automated build from a source control repository for bundling required artifacts as an installable unit. The build configuration module fetches the source code from the source control repository, where the fetched source code is further loaded into a build server. The build server performs the compilation process which converts the source into binaries. Upon completion of the compilation process, a predefined set of batch files which contain the specific command and instruction will be trigged by the build process to package the required binaries and base binding files and configuration files to form a unit of installable generally termed as installer package. Thus, after bundling the required artifacts, said build configuration module configures the installer package file, wherein said installer package file contains all the required artifacts. The automated build use the build definition, xml pre-processing instructions, the power shell/Ant scripts, batch files and command line tools to create a binary file. The installer package file is used-as-a-service-deliverable for the deployment stage—The— said service deliverables further includes schema, maps, orchestrations, pipeline, and helper libraries satisfying the pre-requisites for deploying the services. Based on the service deliverables, a deployment module upon execution of the processor is configured to execute the deployment process in a single click action.
The single click action of the deployment tool is configured to trigger execution of plurality of cascaded tasks in predetermined sequence, wherein said tasks are executed by corresponding deployment scripts irrespective of node of operation. The cascaded task further comprises of predetermined and pre-sequenced steps such as creating the services in a management console; in this step, the applications will be created in the Enterprise Service Bus (ESB) Management database, wherein said management database stores all the created applications. After creating the applications, step of registering an assembly of services is performed, where all the assemblies are registered in a shared assembly repository called Global Assembly Cache (GAC). During the deployment process, it is ensured that all the assemblies are registered in the GAC. Further, the step of importing appropriate binding file

depending on a host environment is executed. The imported binding files will help in complying with the environment related parameters of the lifted code. As, when the code is moved from one environment to another, the configurations settings, endpoints etc will be changed, and to ensure the compatibility of the lifted code with the environment parameters, said imported binding files are required. This is facilitated with the help of a configuration store database and a scripting task which uses the XML preprocessor for generating the bindings for appropriate environments. Upon importing the appropriate binding files, step of setting up configuration key value pair in configuration database/file is performed, wherein configuration key value pair will be stored in the database used by the ESB server. This will be further accomplished with a combination of powershell/Ant scripts, the XML files with XML preprocessing instructions and the configuration data store. Once the deployment is completed, step of starting the services is performed. This starting of the service will
enlist the service and will start to proeess the incoming messages. Hence, once the
services are started, step of restarting a host instance is performed, wherein the handler or the process which holds the services has to be refreshed to load the latest deployed assemblies.
Thus a multitude of task which needs to be performed for a successful deploy is carried out with a set of instructions triggered by the single click action. During the execution of the deployment process, each encountered error or discrepancy is instantly reported to the user, herein user intervention is soughed, and however, remedial actions may be automated in one of the embodiments of the invention. It acts as an early warning mechanism and helps the user to rectify the issues expeditiously.
A monitoring module comprises of an error detector, log generator and reporting tool and is configured to sequentially monitor the deployment progress. The monitoring module is adapted to maintain log at each stage of the deployment into a file stored at the repository. The reporting tool is adapted to instantaneously access the each update in the log record and render it on a user interface or alternatively communicate to at

least one remote device. Optionally, the monitoring module also configured to
facilitate the user to incorporate on the fly changes within said static and dynamic
configuration settings of the services during deployment by running patch scripts.
After deploying the services along with its parallel monitoring thereof, a verification
module, upon execution of the processor is configured for verifying each service end
points in the plurality of nodes by means of batch file. The deployed services are
verified on the basis of technical verification and functional test. The technical
verification is accomplished with the help of a service ping test with appropriate
command to ensure all the services are up and running. And the functional test is
performed by way of triggering candidate operations within a service with the help of
a sample request message. The verification module also triggers the predefined test
cases to verify each operation of the deployed services. Further, the computer-
implemented system generates a report and verifies the generated result with the
predefined-set of results.
In an another embodiment of the present invention the computer-implemented method is considered to automatically deploy and monitor environment independent services, characterized in having a concurrent deployment execution on the plurality of nodes using a set of deployment scripts. For enabling automation in deployment and monitoring process, set of processor-enabled steps are performed by the processor-executable programmed modules, wherein the said steps includes; configuring an automated build from a source control repository for bundling required artifacts as an installable unit. Upon bundling the required artifacts, step of configuring an installer package file is performed, wherein said installer package file contains all the required artifacts. The installer package file is used as a service deliverable for the deployment stage. The service deliverables further includes schema, maps, orchestrations, pipeline, and helper libraries satisfying the pre¬requisites for deploying the services. Based on the formed service deliverables, step of executing the deployment process with a single click action is performed by the deployment module, one of the processor executable programmed modules. The

single click action triggers the execution of plurality of cascaded tasks in predetermined sequence, wherein said tasks are executed by corresponding deployment scripts irrespective of node of operation.
The cascaded task further comprises of predetermined and pre-sequenced steps such as creating the services in a management console; in this step, the applications will be created in the Enterprise Service Bus (ESB) Management database, wherein said management database stores all the created applications. After creating the applications, step of registering an assembly of services is performed, where all the assemblies are registered in a shared assembly repository called Global Assembly Cache (GAC).During the deployment process, it is ensured that all the assemblies are registered in the GAC. Further, the step of importing appropriate binding file from at least one corresponding binary file thereof depending on a host environment is executed. The imported binding files will help in complying with the environment related parameters of the lifted code. As, when the code is moved from one environment to another, the configurations settings, endpoints etc will be changed, and to ensure the compatibility of the lifted code with the environment parameters, said imported binding files are required. This is facilitated with the help of a configuration store database and a scripting task which uses the XML preprocessor for generating the bindings for appropriate environments. Upon importing the appropriate binding files, step of setting up configuration key value pair in configuration database/file is performed, wherein configuration key value pair will be stored in the database used by the ESB server. This will be further accomplished with a combination of powershell/Ant scripts, the XML files with XML preprocessing instructions and the configuration data store. Once the deployment is completed, step of starting the services is performed. This starting of the service will enlist the service and will start to listen to the incoming messages. Hence, once the services are started, step of restarting a host instance is performed, wherein the handler or the process which holds the services has to be refreshed to load the latest deployed assemblies.

Further, the computer implemented method also prompts the user sequentially for each error or discrepancies which may occur during the deployment process. It acts as an early warning mechanism and helps the user to rectify the issues expeditiously.
In one of the steps of the deployment method, during the deployment process, a side-by-side monitoring step is performed by the monitoring module. The monitoring module sequentially and simultaneously monitors the deployment progress and maintains the log at each stage of the deployment. Optionally, a provision of incorporating on the fly changes within the static and dynamic configuration settings of the services during deployment is facilitated by the monitoring module during monitoring stage by running the patch scripts.
Upon deployment of the services, a step of verification of each service end point is performed by another processor executable programmed module i.e., verification
module. It verifies each service-endpoint the plurality of nodes by means of a batch
file. Further, the verification module also triggers the predefined test cases to verify each operation of the deployed services. The computer-implemented system generates a report and verifies it with the predefined set of results.
Next, the preferred embodiments of the present invention will be described below based on drawings. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions or code. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
Figure 1 is the block diagram of the system (100) illustrating the multiple embodiments of the present invention. The system (100) comprises a processor, a

memory unit coupled with said processor set of instruction stored therein, an automated ESB service deployment and monitoring (102), which is a tool accessible by a user. The said tool (102) further comprises of a set of processor executable programmed modules such as a build configuration module (104), a deployment module (106), a monitoring module (108) and a verification module (110). According to the various embodiments of the present invention, the methods described herein are intended for operation as computer programs modules running on a computer processor.
The build configuration module (102) configures an automated build from a source control repository (116) for bundling required artifacts as an installable unit. Upon bundling the required artifacts, said build configuration module (102) further configures an installer package file (112). The installer package file (112) contains the bundled artifacts. The configured installer package file (112) acts as a service deliverable for the deployment-stage. The service deliverables further includes schema, maps, orchestrations, pipeline, and helper libraries satisfying the pre¬requisites for deploying the services. After configuring the installer package file (112) as the service deliverable, the deployment module (106) is configured to execute the deployment process through a single click action. This module (106) will connect to the Configuration Store (118) to retrieve the environment specific values and bind the values with the target environment during the deployment stage. The single click action triggers or invokes the execution of plurality of cascaded tasks (114) in predetermined sequence. The cascaded tasks (114) are executed by the corresponding deployment scripts of plurality of nodes. The cascaded task (114) further comprises of predetermined and pre-sequenced steps such as creating the services in a management console, wherein the management console stores all the created applications; registering an assembly of services in a shared assembly repository; importing appropriate binding file from at least one corresponding binary file thereof depending on a host environment; setting up configuration key value pair in configuration database/file, wherein configuration key value pair will be stored in the

database used by the ESB server; starting each and every services after completion of deployment of the services; and restarting the host instance. Further, the tool (102) is also capable to prompt the user sequentially for each error or discrepancies which may occur during the deployment stage, it acts as an early warning mechanism and helps the user to rectify the issues expeditiously.
During the deployment process of the services, a parallel monitoring is performed by the monitoring module (108). The monitoring module (108) is configured to perform a sequential and simultaneous monitoring of the deployment progress. The monitoring module (108) also maintains a log at each stage of the deployment. Also, the monitoring module (108) allows the user to incorporate on the fly changes within the static and dynamic configuration Settings of the services during deployment process by running the patch scripts. After deploying the services upon the plurality of nodes, the verification module (110) is configured to verify the each service endpoint in the plurality of nodes by means of a batch file. The verification module (110) also triggers the predefined test cases to verify each operation of the deployed services. The said tool (102) is capable to generate report after deploying, monitoring and verifying the services and further verifies the generated report with predefined set of results.
Figure 2 is the flow diagram (200) illustrating the automated ESB service deployment and monitoring according to one aspect of the present invention. For enabling automation in ESB service deployment and monitoring thereof, various processor executable steps are performed wherein the steps includes; configuring an automated build (202) from a source control repository (116 of figure 1) for bundling required artifacts as an installable unit. After bundling the required artifacts, step of configuring an installer package file (204) is performed. The installer package file having the bundled artifacts is used as a Service deliverable for the deployment stage. The said service deliverables further includes schema, maps, orchestrations, pipeline, and helper libraries satisfying the pre-requisites for deploying the services.

On the basis of the formed service deliverables, step of executing the deployment (206) is performed by the deployment module (106 of figure 1) by retrieving the configuration values from the configuration store (118) for the target environment, The deployment process is executed through a single click action. The single click action triggers the executing of cascaded tasks (208) in a sequenced manner, wherein said tasks are executed by corresponding deployment scripts on the plurality of nodes. The cascaded task further comprises of predetermined and pre-sequenced steps such as creating the services in a management console; registering an assembly of services; deploying the assembly into an application repository; importing appropriate binding file from at least one corresponding binary file thereof depending on a host environment; setting up configuration key value pair in configuration database/file; starting the services; and restarting the host instance. Also the tool (102 of figure 1) is capable for prompting the user for error or discrepancies (210) sequentially which may occur during the deployment process. Prompting the user acts as an-early warning mechanism and helps the user to rectify the issues expeditiously.
Along with the execution of the deployment process, the step of monitoring the deployment progress and maintaining the log (212) is performed by the monitoring module (108 of figure 1). The log is maintained at each stage of the deployment. Optionally, the tool (102 of Figure 1) also enables a step of incorporating on the fly changes (214) within the static and dynamic configuration settings of the services during deployment.
Upon deployment of the services, step of verifying service endpoints (216) are performed by the verification module (110 of figure 1). It verifies each service endpoint in the plurality of nodes by means of a batch file. Further, the verification module also triggers the predefined test cases to verify each operation of the deployed services. The computer-implemented system generates a report and verifies it with the predefined set of results.

The methodology and techniques described with respect to the exemplary embodiments can be performed using a computer-implemented system or other computing device within which a set of instructions, when executed, may cause the said computer-implemented system to perform any one or more of the methodologies discussed above. The said computer-implemented system may include a processor embedded within the said computer-implemented system which is configured for executing the said programmed instructions or the said set of instructions. The said computer-implemented system is configured from different modules; each module is configured for executing programmed instructions or set of instruction to perform a particular task. According to the embodiments of the present invention, the computer-implemented system may also operate as a standalone device.
In accordance with various embodiments of the present disclosure, the methods described herein are intended for operation as- software programs running on-a computer processor - [processor embedded within the said computer-implemented system].
Although the invention has been described in terms of specific embodiments and applications, persons skilled in the art can, in light of this teaching, generate additional embodiments without exceeding the scope or departing from the spirit of the invention described herein.

We Claim:
1. A method for environment independent service deployment, characterized in a concurrent deployment execution on a plurality of node using a set of deployment script and parallel monitoring thereof, the method comprising processor implemented steps of:
a. configuring an automated build from a source control repository for
bundling required artifacts as an installable unit;
b. configuring an installer package file containing the bundled artifacts
and binding files of a plurality of environment to form services
deliverables;
c. executing the deployment with a single click action, wherein said
single click triggers an execution of-a-plurality-of cascaded tasks in a
predetermined sequence such that said tasks are executed by a corresponding deployment script irrespective of node of operation thereof;
d. deploying the services in a manner such that the user is prompted
sequentially for each error or discrepancies therein;
e. monitoring sequentially a deployment progress log at each stage of the
deployment and optionally incorporating on the fly, dynamic changes
therein properties of environment and the deliverables; and
f. verifying each service end point in the plurality of nodes by means of a
batch file and testing deployment completeness, and latencies in
message processing.
2. The method as claimed in claim 1, wherein the cascaded tasks comprises of:
a. creating the services in a management console, wherein said management
console stores all the created Services on the ESB;
b. registering an assembly of services in a shared assembly repository;

c. importing appropriate binding file from at least one corresponding binary
file thereof depending on a host environment;
d. setting up configuration key value pair in configuration database/file,
wherein configuration key value pair will be stored in the database used by
the ESB server;
e. upon completion of the deployment of the services, starting each and
every services; and
f. restarting a host instance.
3. The method as claimed in claim 1, wherein said binding files of a plurality of environment are accomplished at the point of deployment based on a central configuration store, wherein said central configuration store further maintains all the environment specific key value pair for different environments.
4. The method as claimed in claim 1, wherein said environment includes static and dynamic configuration settings such as URL, server name, user/group settings, credentials or combination thereof.
5. The method as claimed in claim 1, wherein said deliverables further includes schema, maps, orchestrations, pipeline, helper libraries.
6. The method as claimed in claim 1, wherein said automated build use the build definition, xml pre-processing instructions, the power shell/Ant scripts, batch files and command line tools to create a binary file thereof.
7. The method as claimed in claim 1, wherein during each deployment execution a service code is initially installed on the each primary node and subsequently replicated on the corresponding secondary nodes thereof by using replication logic.

8. A system for environment independent service deployment, characterized in having a set of a deployment script enabled for concurrent deployment execution on a plurality of node and parallel monitoring thereof, the system comprising:
a. a memory unit for storing a set of instructions;
b. a processor coupled to said memory unit, wherein said processor,
responsive to said set of instructions is further configured to enable;
c. a build configuration module to:
i. configure an automated build from a source control repository for
bundling required artifacts as an installable unit; and ii. configure an installer package file containing the bundled artifacts and binding files of a plurality of environment to form
services/application deliverables;
' d. a deployment module configured to: '"
i. execute the deployment with a single click action based on the formed service deliverables, wherein said single click triggers an execution of a plurality of cascaded tasks in a predetermined sequence such that said tasks are executed by a corresponding deployment script irrespective of node of operation thereof; and ii. prompt the user sequentially for each error or discrepancies which may occur during deployment of the services;
e. a monitoring module configured to monitor sequentially a deployment
progress log at each stage of the deployment and optionally incorporate on
the fly, running patch scripts, dynamic changes therein properties of
environment and the deliverables; and
f. a verification module configured to verify each service end point in the
plurality of nodes by means of a batch file and testing deployment
completeness, and latencies in message processing.

9. The system as claimed in claim 8, wherein the cascaded tasks comprises of:
a. creating the services in a management console, wherein said management
console stores all the created applications on the ESB;
b. registering an assembly of services in a shared assembly repository;
c. importing appropriate binding file from at least one corresponding binary
file thereof depending on a host environment;
d. setting up configuration key value pair in configuration database/file,
wherein configuration key value pair will be stored in the database used by
the ESB server;
e. Upon completion of the deployment of the services, starting each and
every services; and
f. restarting a host instance.
10. The system as claimed in-claim 8, wherein-said binding files of a plurality of-environment are accomplished at the point of deployment based on a central configuration store, wherein said central configuration store further maintains all the environment specific key value pair for different environments.
11. The system for environment independent service/application deployment as claimed in claim 8, wherein said environment includes static and dynamic configuration settings such as URL, server name, user/group settings, credentials or combination thereof.
12. The system for environment independent service/application deployment as claimed in claim 8, wherein said deliverables further includes schema, maps, orchestrations, pipeline, helper libraries.
13. The system as claimed in claim 8, wherein said automated build use the build definition, xml pre-processing instructions, the power shell/Ant scripts, batch files and command line tools to create a binary file thereof.

14. The system as claimed in claim 8; wherein during each deployment execution a service code is initially installed on the each primary node and subsequently replicated on the corresponding secondary nodes thereof by using a replication logic