AWS m2 documentation change
Summary
Updated product name references from 'AWS Blu Age' to 'AWS Transform for mainframe' throughout the documentation
Security assessment
The changes are purely branding/product name updates without any mention of security vulnerabilities, security features, or security-related improvements. The updates replace 'Blu Age' with 'Transform for mainframe' in technical context but do not introduce or modify security controls, configurations, or advisories.
Diff
diff --git a/m2/latest/userguide/ba-shared-structure.md b/m2/latest/userguide/ba-shared-structure.md index 5e0d63c62..ea47be8ef 100644 --- a//m2/latest/userguide/ba-shared-structure.md +++ b//m2/latest/userguide/ba-shared-structure.md @@ -9 +9 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -# AWS Blu Age structure of a modernized application +# AWS Transform for mainframe structure of a modernized application @@ -28 +28 @@ We assume that you already have basic knowledge about the following: - * Throughout the document, we use `short class names` for readability. For more information, see AWS Blu Age fully qualified name mappings to retrieve the corresponding fully qualified names for AWS Blu Age runtime elements and Third party fully qualified name mappings to retrieve the corresponding fully qualified names for third party elements. + * Throughout the document, we use `short class names` for readability. For more information, see AWS Transform for mainframe fully qualified name mappings to retrieve the corresponding fully qualified names for AWS Transform for mainframe runtime elements and Third party fully qualified name mappings to retrieve the corresponding fully qualified names for third party elements. @@ -50 +50 @@ We assume that you already have basic knowledge about the following: -AWS Blu Age modernized applications are packaged as java web applications (.war), that you can deploy on a JEE server. Typically, the server is a [Tomcat](https://tomcat.apache.org/) instance that embeds the AWS Blu Age Runtime, which is currently built upon the [Springboot](https://spring.io/projects/spring-boot) and [Angular](https://angular.io/) (for the UI part) frameworks. +AWS Transform for mainframe modernized applications are packaged as java web applications (.war), that you can deploy on a JEE server. Typically, the server is a [Tomcat](https://tomcat.apache.org/) instance that embeds the AWS Transform for mainframe Runtime, which is currently built upon the [Springboot](https://spring.io/projects/spring-boot) and [Angular](https://angular.io/) (for the UI part) frameworks. @@ -75 +75 @@ The following descriptions only apply to COBOL and PL/I modernization outputs. R -Before any refactoring, the packages organization in the entities project is tied to the modernized programs. You can accomplish this in a couple of different ways. The preferred way is to use the Refactoring toolbox, which operates before you trigger the code generation mechanism. This is an advanced operation, which is explained in the BluAge trainings. For more information, see [Refactoring workshop](https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/refactoring). This approach allows you to preserve the capability to re-generate the java code later, to benefit from further improvements in the future, for instance). The other way is to do regular java refactoring, directly on the generated source code, using any java refactoring approach you might like to apply -- at your own risk. +Before any refactoring, the packages organization in the entities project is tied to the modernized programs. You can accomplish this in a couple of different ways. The preferred way is to use the Refactoring toolbox, which operates before you trigger the code generation mechanism. This is an advanced operation, which is explained in the AWS Transform for mainframe trainings. For more information, see [Refactoring workshop](https://catalog.workshops.aws/aws-blu-age-l3-certification-workshop/en-US/refactoring). This approach allows you to preserve the capability to re-generate the java code later, to benefit from further improvements in the future, for instance). The other way is to do regular java refactoring, directly on the generated source code, using any java refactoring approach you might like to apply -- at your own risk. @@ -97 +97 @@ The business.context sub-package contains two classes, a configuration class and -The model sub-package contains all the data structures that the given program can use. For instance, any 01 level COBOL data structure corresponds to a class in the model sub-package (lower level data structures are properties of their owning 01 level structure). For more information about how we modernize 01 data structures, see [What are data simplifiers in AWS Blu Age](./ba-shared-data.html). +The model sub-package contains all the data structures that the given program can use. For instance, any 01 level COBOL data structure corresponds to a class in the model sub-package (lower level data structures are properties of their owning 01 level structure). For more information about how we modernize 01 data structures, see [What are data simplifiers in AWS Transform for mainframe](./ba-shared-data.html). @@ -139 +139 @@ The most exhaustive case will have three packages: - * `_base package_._program_.service.impl`: contains a class named _Program_ ProcessImpl, which is the implementation of the Process interface described previously. This is where the legacy statements are "translated" to java statements, relying on the AWS Blu Age framework: + * `_base package_._program_.service.impl`: contains a class named _Program_ ProcessImpl, which is the implementation of the Process interface described previously. This is where the legacy statements are "translated" to java statements, relying on the AWS Transform for mainframe framework: @@ -186 +186 @@ In addition to program related artifacts, the service project can contain other -The Blu Age runtime consumes those json files to bind the records used by the SEND MAP statement with the screen fields. +The AWS Transform for mainframe runtime consumes those json files to bind the records used by the SEND MAP statement with the screen fields. @@ -225 +225 @@ The web project is only present when modernizing legacy UI elements. The modern -The web project only takes care of the front end aspect of the application The service project, which relies on the utility and entities projects, provides the backend services. The link between the front end and the backend is made through the web application named Gapwalk-Application, which is part of the standard AWS Blu Age runtime distribution. +The web project only takes care of the front end aspect of the application The service project, which relies on the utility and entities projects, provides the backend services. The link between the front end and the backend is made through the web application named Gapwalk-Application, which is part of the standard AWS Transform for mainframe runtime distribution. @@ -243 +243 @@ In this example, the program is registered once, under the name 'CBACT04C' (look -The same registration mechanism applies to utility programs brought by the various utility AWS Blu Age web applications, which are part of the AWS Blu Age runtime distribution. For instance, the Gapwalk-Utility-Pgm webapp provides the functional equivalents of the z/OS system utilities (IDCAMS, ICEGENER, SORT,and so on) and can be called by modernized programs or scripts. All available utility programs that are registered at Tomcat startup are logged in the Tomcat logs. +The same registration mechanism applies to utility programs brought by the various utility AWS Transform for mainframe web applications, which are part of the AWS Transform for mainframe runtime distribution. For instance, the Gapwalk-Utility-Pgm webapp provides the functional equivalents of the z/OS system utilities (IDCAMS, ICEGENER, SORT,and so on) and can be called by modernized programs or scripts. All available utility programs that are registered at Tomcat startup are logged in the Tomcat logs. @@ -377 +377 @@ Creating an unmodifiable set of identifiers in the program is one way of doing t -The program needs a companion `RuntimeContext` instance. For modernized programs, AWS Blu Age automatically generates the companion context, using the data structures that are part of the legacy program. +The program needs a companion `RuntimeContext` instance. For modernized programs, AWS Transform for mainframe automatically generates the companion context, using the data structures that are part of the legacy program. @@ -471 +471 @@ When you're sure that your program is properly registered, you can start iterati -This section contains lists of the AWS Blu Age and third-party fully qualified name mappings for use in your modernized applications. +This section contains lists of the AWS Transform for mainframe and third-party fully qualified name mappings for use in your modernized applications. @@ -473 +473 @@ This section contains lists of the AWS Blu Age and third-party fully qualified n -### AWS Blu Age fully qualified name mappings +### AWS Transform for mainframe fully qualified name mappings