AWS m2 documentation change
Summary
Updated branding from 'AWS Blu Age' to 'AWS Transform for mainframe' throughout the documentation
Security assessment
Changes consist solely of product name updates from 'AWS Blu Age' to 'AWS Transform for mainframe'. No security-related content modifications, vulnerability fixes, or new security features are introduced.
Diff
diff --git a/m2/latest/userguide/ba-shared-architecture.md b/m2/latest/userguide/ba-shared-architecture.md index 5e05931ae..cd27fee66 100644 --- a//m2/latest/userguide/ba-shared-architecture.md +++ b//m2/latest/userguide/ba-shared-architecture.md @@ -5 +5 @@ -AWS Blu Age runtime componentsExecution environmentsStatelessness and session handlingHigh availability and statelessness +AWS Transform for mainframe runtime componentsExecution environmentsStatelessness and session handlingHigh availability and statelessness @@ -9 +9 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -# AWS Blu Age Runtime high level architecture +# AWS Transform for mainframe Runtime high level architecture @@ -11 +11 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -As a part of the AWS Blu Age solution for modernizing legacy programs to Java, the AWS Blu Age Runtime provides a unified, REST-based entry point for modernized applications, and a framework of execution for such applications, through libraries providing legacy constructs and a standardization of programs code organization. +As a part of the AWS Transform for mainframe solution for modernizing legacy programs to Java, the AWS Transform for mainframe Runtime provides a unified, REST-based entry point for modernized applications, and a framework of execution for such applications, through libraries providing legacy constructs and a standardization of programs code organization. @@ -13 +13 @@ As a part of the AWS Blu Age solution for modernizing legacy programs to Java, t -Such modernized applications are the result of the AWS Blu Age Automated Refactor process for modernizing mainframe and midrange programs (referred to in the following document as "legacy") to a web based architecture. +Such modernized applications are the result of the AWS Transform for mainframe Automated Refactor process for modernizing mainframe and midrange programs (referred to in the following document as "legacy") to a web based architecture. @@ -15 +15 @@ Such modernized applications are the result of the AWS Blu Age Automated Refacto -The AWS Blu Age Runtime goals are reproduction of legacy programs behavior (isofunctionality), performances (with respect to programs execution time and resources consumption), and ease of maintenance of modernized programs by Java developers, though the use of familiar environments and idioms such as tomcat, Spring, getters/setters, fluent APIs. +The AWS Transform for mainframe Runtime goals are reproduction of legacy programs behavior (isofunctionality), performances (with respect to programs execution time and resources consumption), and ease of maintenance of modernized programs by Java developers, though the use of familiar environments and idioms such as tomcat, Spring, getters/setters, fluent APIs. @@ -19 +19 @@ The AWS Blu Age Runtime goals are reproduction of legacy programs behavior (isof - * AWS Blu Age runtime components + * AWS Transform for mainframe runtime components @@ -30 +30 @@ The AWS Blu Age Runtime goals are reproduction of legacy programs behavior (isof -## AWS Blu Age runtime components +## AWS Transform for mainframe runtime components @@ -32 +32 @@ The AWS Blu Age Runtime goals are reproduction of legacy programs behavior (isof -The AWS Blu Age Runtime environment is composed of two kinds of components: +The AWS Transform for mainframe Runtime environment is composed of two kinds of components: @@ -43 +43 @@ The following sections detail the role of both of these components. -### AWS Blu Age libraries +### AWS Transform for mainframe libraries @@ -45 +45 @@ The following sections detail the role of both of these components. -The AWS Blu Age libraries are a set of jar files stored in a `shared/` subfolder added to the standard tomcat classpath, so as to make them available to all modernized Java programs. Their goal is to provide features that are neither natively nor easily available in the Java programming environment, but typical of legacy development environments. Those features are exposed in a way that is as familiar as possible to Java developers (getters/setters, class-based, fluent APIs). An important example is the **Data Simplifier** library, which provides legacy memory layout and manipulation constructs (encountered in COBOL, PL1 or RPG languages) to Java programs. Those jars are a core dependency of the modernized Java code generated from legacy programs. For more information about the Data Simplifier, see [What are data simplifiers in AWS Blu Age](./ba-shared-data.html). +The AWS Transform for mainframe libraries are a set of jar files stored in a `shared/` subfolder added to the standard tomcat classpath, so as to make them available to all modernized Java programs. Their goal is to provide features that are neither natively nor easily available in the Java programming environment, but typical of legacy development environments. Those features are exposed in a way that is as familiar as possible to Java developers (getters/setters, class-based, fluent APIs). An important example is the **Data Simplifier** library, which provides legacy memory layout and manipulation constructs (encountered in COBOL, PL1 or RPG languages) to Java programs. Those jars are a core dependency of the modernized Java code generated from legacy programs. For more information about the Data Simplifier, see [What are data simplifiers in AWS Transform for mainframe](./ba-shared-data.html). @@ -49 +49 @@ The AWS Blu Age libraries are a set of jar files stored in a `shared/` subfolder -Web Application Archives (WARs) are a standard way of deploying code and applications to the tomcat application server. The ones provided as part of the AWS Blu Age runtime aim at providing a set of execution frameworks reproducing legacy environments and transaction monitors (JCL batches, CICS, IMS...), and associated required services. +Web Application Archives (WARs) are a standard way of deploying code and applications to the tomcat application server. The ones provided as part of the AWS Transform for mainframe runtime aim at providing a set of execution frameworks reproducing legacy environments and transaction monitors (JCL batches, CICS, IMS...), and associated required services. @@ -51 +51 @@ Web Application Archives (WARs) are a standard way of deploying code and applica -The most important one is `gapwalk-application` (often shortened as "Gapwalk"), which provides a unified set of REST-based entry points to trigger and control transactions, programs and batches execution. For more information, see [AWS Blu Age Runtime APIs](./ba-runtime-endpoints.html). +The most important one is `gapwalk-application` (often shortened as "Gapwalk"), which provides a unified set of REST-based entry points to trigger and control transactions, programs and batches execution. For more information, see [AWS Transform for mainframe Runtime APIs](./ba-runtime-endpoints.html). @@ -66 +66 @@ Other web applications add to the execution environment (more precisely, to the -To participate in and take advantage of those constructs, frameworks and services, Java programs modernized from legacy ones adhere to a specific structure documented in [AWS Blu Age structure of a modernized application](./ba-shared-structure.html). At startup, the AWS Blu Age Runtime will collect all such programs in a common "Programs Registry" so that they can be invoked (and call each other) afterwards. The Program Registry provides loose coupling and possibilities of decomposition (since programs calling each other do not have to be modernized simultaneously). +To participate in and take advantage of those constructs, frameworks and services, Java programs modernized from legacy ones adhere to a specific structure documented in [AWS Transform for mainframe structure of a modernized application](./ba-shared-structure.html). At startup, the AWS Transform for mainframe Runtime will collect all such programs in a common "Programs Registry" so that they can be invoked (and call each other) afterwards. The Program Registry provides loose coupling and possibilities of decomposition (since programs calling each other do not have to be modernized simultaneously). @@ -74 +74 @@ Frequently encountered legacy environments and choreographies are available: - * A AWS Blu Age subsystem provides an execution environment similar to CICS through: + * A AWS Transform for mainframe subsystem provides an execution environment similar to CICS through: @@ -108 +108 @@ All of those environments build upon common OS-level services such as: -An important feature of the AWS Blu Age Runtime is to enable High Availability (HA) and horizontal scalability scenarios when executing modernized programs. +An important feature of the AWS Transform for mainframe Runtime is to enable High Availability (HA) and horizontal scalability scenarios when executing modernized programs. @@ -127 +127 @@ Tomcat being web-based, an important mechanism for this is HTTP session handling -Cookie management is done automatically by the AWS Blu Age framework and the underlying tomcat server, this is transparent to the user. The user internet browser will manage this automatically. +Cookie management is done automatically by the AWS Transform for mainframe framework and the underlying tomcat server, this is transparent to the user. The user internet browser will manage this automatically. @@ -142 +142 @@ The Gapwalk web application may store the session state (the context) in various -More generally, a design tenet of the AWS Blu Age framework is statelessness: most non-transient states required to reproduce legacy programs behavior are not stored inside the application servers, but shared through an external, common "single source of truth". +More generally, a design tenet of the AWS Transform for mainframe framework is statelessness: most non-transient states required to reproduce legacy programs behavior are not stored inside the application servers, but shared through an external, common "single source of truth". @@ -156 +156 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -AWS Blu Age Runtime concepts +AWS Transform for mainframe Runtime concepts