AWS m2 documentation change
Summary
Updated product name from 'AWS Blu Age' to 'AWS Transform for mainframe' throughout the documentation, including references to runtime components, APIs, and tooling. Updated links and terminology to reflect rebranding.
Security assessment
The changes primarily involve a product name rebranding (Blu Age -> Transform for mainframe) with no modifications to security-related content. No vulnerabilities, mitigations, or new security features are introduced. Existing security mechanisms (e.g., secrets managers, authentication) descriptions remain unchanged except for naming updates.
Diff
diff --git a/m2/latest/userguide/ba-faq.md b/m2/latest/userguide/ba-faq.md index 28ef0960a..5d1896a1f 100644 --- a//m2/latest/userguide/ba-faq.md +++ b//m2/latest/userguide/ba-faq.md @@ -5 +5 @@ -GeneralAWS Blu Age RuntimeDataTransformationDeploymentSecurity +GeneralAWS Transform for mainframe RuntimeDataTransformationDeploymentSecurity @@ -9 +9 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -# AWS Blu Age FAQ +# AWS Transform for mainframe FAQ @@ -13 +13 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is - 1. **What is the main purpose of AWS Blu Age Refactoring capability?** + 1. **What is the main purpose of AWS Transform for mainframe Refactoring capability?** @@ -17 +17 @@ The refactoring capability refactors legacy monolithic code into java using cont - 2. **Which mainframe applications are supported by AWS Blu Age?** + 2. **Which mainframe applications are supported by AWS Transform for mainframe?** @@ -19 +19 @@ The refactoring capability refactors legacy monolithic code into java using cont -AWS Blu Age currently supports the modernization of IBM z/OS mainframe applications written in COBOL, PL/I, JCL (Job Control Language) and relying on CICS (Customer Information Control System) transaction manager, BMS (Basic Mapping Support) screens, IMS MFS Screens, DB2 databases, IMS databases, Flat files, GDG (Generation data groups) and VSAM (Virtual Storage Access Method) data files. +AWS Transform for mainframe currently supports the modernization of IBM z/OS mainframe applications written in COBOL, PL/I, JCL (Job Control Language) and relying on CICS (Customer Information Control System) transaction manager, BMS (Basic Mapping Support) screens, IMS MFS Screens, DB2 databases, IMS databases, Flat files, GDG (Generation data groups) and VSAM (Virtual Storage Access Method) data files. @@ -21 +21 @@ AWS Blu Age currently supports the modernization of IBM z/OS mainframe applicati - 3. **What mainframe languages can AWS Blu Age modernize?** + 3. **What mainframe languages can AWS Transform for mainframe modernize?** @@ -23 +23 @@ AWS Blu Age currently supports the modernization of IBM z/OS mainframe applicati -AWS Blu Age transforms COBOL and PL/I code to Java, JCLs to Groovy, screens (BMS or MFS) to HTML (with Sass) and JavaScript (Angular applications – React is not supported for now), enabling the modernization of legacy mainframe applications to cloud-native architectures. These technologies are chosen for their widespread adoption, robust ecosystem, and cloud-native capabilities. Angular provides a modern, responsive user interface layer that replaces legacy green-screen interfaces. It enables the creation of dynamic, user-friendly web applications that can be accessed across different devices and platforms. Its component-based architecture supports maintainable and scalable front-end development. The transformation results in distributed applications that follow modern architectural patterns and best practices. +AWS Transform for mainframe transforms COBOL and PL/I code to Java, JCLs to Groovy, screens (BMS or MFS) to HTML (with Sass) and JavaScript (Angular applications – React is not supported for now), enabling the modernization of legacy mainframe applications to cloud-native architectures. These technologies are chosen for their widespread adoption, robust ecosystem, and cloud-native capabilities. Angular provides a modern, responsive user interface layer that replaces legacy green-screen interfaces. It enables the creation of dynamic, user-friendly web applications that can be accessed across different devices and platforms. Its component-based architecture supports maintainable and scalable front-end development. The transformation results in distributed applications that follow modern architectural patterns and best practices. @@ -25 +25 @@ AWS Blu Age transforms COBOL and PL/I code to Java, JCLs to Groovy, screens (BMS - 4. **How does AWS Blu Age balance legacy constraints with cloud benefits?** + 4. **How does AWS Transform for mainframe balance legacy constraints with cloud benefits?** @@ -27 +27 @@ AWS Blu Age transforms COBOL and PL/I code to Java, JCLs to Groovy, screens (BMS -AWS Blu Age achieves balance by preserving critical business logic and functionality while introducing cloud-native capabilities. It ensures that modernized applications maintain necessary legacy business logic while taking advantage of cloud scalability, agility, and modern operational practices. This approach helps organizations maintain business continuity while gaining the benefits of cloud infrastructure. +AWS Transform for mainframe achieves balance by preserving critical business logic and functionality while introducing cloud-native capabilities. It ensures that modernized applications maintain necessary legacy business logic while taking advantage of cloud scalability, agility, and modern operational practices. This approach helps organizations maintain business continuity while gaining the benefits of cloud infrastructure. @@ -31 +31 @@ AWS Blu Age achieves balance by preserving critical business logic and functiona -Service-oriented architecture plays a fundamental role in breaking down monolithic applications into more manageable modular components. AWS Blu Age creates service-oriented and object-oriented applications that facilitate better maintainability and scalability. This architectural approach enables organizations to achieve greater business efficiency and prepare for potential future microservices adoption. +Service-oriented architecture plays a fundamental role in breaking down monolithic applications into more manageable modular components. AWS Transform for mainframe creates service-oriented and object-oriented applications that facilitate better maintainability and scalability. This architectural approach enables organizations to achieve greater business efficiency and prepare for potential future microservices adoption. @@ -37 +37 @@ The refactoring process includes the complete software stack: application code, - 7. **Does the AWS Blu Age modernization process eliminate the need for any testing or quality assurance checks on the modernized Java application?** + 7. **Does the AWS Transform for mainframe modernization process eliminate the need for any testing or quality assurance checks on the modernized Java application?** @@ -39 +39 @@ The refactoring process includes the complete software stack: application code, -No, the AWS Blu Age modernization process doesn't eliminate the need for any testing or quality assurance checks on the modernized Java application. +No, the AWS Transform for mainframe modernization process doesn't eliminate the need for any testing or quality assurance checks on the modernized Java application. @@ -41 +41 @@ No, the AWS Blu Age modernization process doesn't eliminate the need for any tes - 8. **What does AWS Blu Age JAC stand for?** + 8. **What does AWS Transform for mainframe JAC stand for?** @@ -45 +45 @@ JAC stands for JICS Administration Console - 9. **How can I access the AWS Blu Age tooling?** + 9. **How can I access the AWS Transform for mainframe tooling?** @@ -47 +47 @@ JAC stands for JICS Administration Console -AWS Blu Age tooling is accessible through the AWS Console via AWS Mainframe Modernization (M2) Refactor, with feature access based on your accreditation level. Start with the Transformation Center to assess automatic Java refactoring of your source code. For detailed guidance, refer to the [AWS AWS Transform for mainframe refactor](https://bluinsights.aws/) documentation. After modernization, you can deploy applications using runtime. For more information, see [AWS Mainframe Modernization documentation](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-options.html). +AWS Transform for mainframe tooling is accessible through the AWS Console via AWS Mainframe Modernization (M2) Refactor, with feature access based on your accreditation level. Start with the Transformation Center to assess automatic Java refactoring of your source code. For detailed guidance, refer to the [AWS Transform for mainframe refactor](https://bluinsights.aws/) documentation. After modernization, you can deploy applications using runtime. For more information, see [AWS Mainframe Modernization documentation](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-options.html). @@ -51 +51 @@ AWS Blu Age tooling is accessible through the AWS Console via AWS Mainframe Mode -See [AWS AWS Transform for mainframe refactor Estimates](https://bluinsights.aws/docs/business-estimate/) for more information on this or work with your Account Manager. +See [AWS Transform for mainframe refactor Estimates](https://bluinsights.aws/docs/business-estimate/) for more information on this or work with your Account Manager. @@ -53 +53 @@ See [AWS AWS Transform for mainframe refactor Estimates](https://bluinsights.aws - 11. **Are there specific requirements to maintain Java AWS Blu Age migrated solutions?** + 11. **Are there specific requirements to maintain Java AWS Transform for mainframe migrated solutions?** @@ -55 +55 @@ See [AWS AWS Transform for mainframe refactor Estimates](https://bluinsights.aws -No, there are no specific requirements to maintain Java AWS Blu Age migrated solutions. +No, there are no specific requirements to maintain Java AWS Transform for mainframe migrated solutions. @@ -57 +57 @@ No, there are no specific requirements to maintain Java AWS Blu Age migrated sol - 12. **What are the technical specifications and compatibility of AWS Blu Age generated code?** + 12. **What are the technical specifications and compatibility of AWS Transform for mainframe generated code?** @@ -59 +59 @@ No, there are no specific requirements to maintain Java AWS Blu Age migrated sol -AWS Blu Age generated code is designed with specific technical characteristics and broad compatibility. While it doesn't support JPA, it uses direct SQL execution with externalized queries. The code relies on runtime-specific libraries for functional equivalence, web services generation, and MQ implementations. The generated code can be imported into any Java IDE for development, testing, building, and deployment, though required libraries must be imported accordingly. While Maven is integrated by default with AWS Mainframe Modernization service for build processes, alternative tools like Gradle can be used by modifying the packaging format after transformation. The platform offers flexibility in terms of development tools and source control, with training available for development teams managing the code. For more information, see [AWS Blu Age Runtime high level architecture](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html). +AWS Transform for mainframe generated code is designed with specific technical characteristics and broad compatibility. While it doesn't support JPA, it uses direct SQL execution with externalized queries. The code relies on runtime-specific libraries for functional equivalence, web services generation, and MQ implementations. The generated code can be imported into any Java IDE for development, testing, building, and deployment, though required libraries must be imported accordingly. While Maven is integrated by default with AWS Mainframe Modernization service for build processes, alternative tools like Gradle can be used by modifying the packaging format after transformation. The platform offers flexibility in terms of development tools and source control, with training available for development teams managing the code. For more information, see [AWS Transform for mainframe Runtime high level architecture](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html). @@ -64 +64 @@ AWS Blu Age generated code is designed with specific technical characteristics a -## AWS Blu Age Runtime +## AWS Transform for mainframe Runtime @@ -66 +66 @@ AWS Blu Age generated code is designed with specific technical characteristics a - 1. **Where can I find information about AWS Blu Age Runtime?** + 1. **Where can I find information about AWS Transform for mainframe Runtime?** @@ -68 +68 @@ AWS Blu Age generated code is designed with specific technical characteristics a -Refer the [Set up AWS Blu Age Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-setup.html) documentation runtime that details set-up process onboarding, retrieving artifacts, deployment, etc. +Refer the [Set up AWS Transform for mainframe Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-setup.html) documentation runtime that details set-up process onboarding, retrieving artifacts, deployment, etc. @@ -70 +70 @@ Refer the [Set up AWS Blu Age Runtime](https://docs.aws.amazon.com/m2/latest/use - 2. **Are the AWS Blu Age JAR dependencies uploaded to the client's Maven Repository for local development?** + 2. **Are the AWS Transform for mainframe JAR dependencies uploaded to the client's Maven Repository for local development?** @@ -72 +72 @@ Refer the [Set up AWS Blu Age Runtime](https://docs.aws.amazon.com/m2/latest/use -Libraries can be imported into EC2 using an AMI which can be used for configuring Development, Test & Production environment. Training & enablement will be given to the team to maintain/enhance the generated application code. For more information, see [AWS Blu Age Runtime high level architecture](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html). +Libraries can be imported into EC2 using an AMI which can be used for configuring Development, Test & Production environment. Training & enablement will be given to the team to maintain/enhance the generated application code. For more information, see [AWS Transform for mainframe Runtime high level architecture](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html). @@ -74 +74 @@ Libraries can be imported into EC2 using an AMI which can be used for configurin - 3. **What does the term “Gapwalk” refer to in the distributed AWS Blu Age Runtime jars?** + 3. **What does the term “Gapwalk” refer to in the distributed AWS Transform for mainframe Runtime jars?** @@ -76 +76 @@ Libraries can be imported into EC2 using an AMI which can be used for configurin -For information on Gapwalk, see [AWS Blu Age Runtime artifacts ](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-artifacts.html). +For information on Gapwalk, see [AWS Transform for mainframe Runtime artifacts ](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-artifacts.html). @@ -78 +78 @@ For information on Gapwalk, see [AWS Blu Age Runtime artifacts ](https://docs.aw - 4. **How to request access to the AWS Blu Age Runtime ?** + 4. **How to request access to the AWS Transform for mainframe Runtime ?** @@ -80 +80 @@ For information on Gapwalk, see [AWS Blu Age Runtime artifacts ](https://docs.aw -The Runtime is accessible through the [Blu Age Toolbox](https://bluinsights.aws/docs/bluage-toolbox-introduction) on AWS Transform for mainframe refactor. +The Runtime is accessible through the [AWS Transform for mainframe Toolbox](https://bluinsights.aws/docs/bluage-toolbox-introduction) on AWS Transform for mainframe refactor. @@ -82 +82 @@ The Runtime is accessible through the [Blu Age Toolbox](https://bluinsights.aws/ - 5. **What are the supported Runtimes for AWS Blu Age refactored applications?** + 5. **What are the supported Runtimes for AWS Transform for mainframe refactored applications?** @@ -84 +84 @@ The Runtime is accessible through the [Blu Age Toolbox](https://bluinsights.aws/ -AWS Blu Age offers a single Runtime to cater to different stages of your modernization journey and operational needs see [AWSBlu Age Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-options.html). +AWS Transform for mainframe offers a single Runtime to cater to different stages of your modernization journey and operational needs see [AWS Transform for mainframe Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-runtime-options.html). @@ -86 +86 @@ AWS Blu Age offers a single Runtime to cater to different stages of your moderni - 6. **When is the AWS Blu Age Runtime used?** + 6. **When is the AWS Transform for mainframe Runtime used?** @@ -88 +88 @@ AWS Blu Age offers a single Runtime to cater to different stages of your moderni -An AWS Blu Age Runtime is necessary to support the execution of AWS Blu Age refactored applications. A runtime is necessary during AWS Blu Age-based refactoring projects for testing the refactored applications. Once refactoring project is over, a runtime is also needed for maintaining, testing, and running AWS Blu Age refactored applications in production. +An AWS Transform for mainframe Runtime is necessary to support the execution of AWS Transform for mainframe refactored applications. A runtime is necessary during AWS Transform for mainframe-based refactoring projects for testing the refactored applications. Once refactoring project is over, a runtime is also needed for maintaining, testing, and running AWS Transform for mainframe refactored applications in production. @@ -90 +90 @@ An AWS Blu Age Runtime is necessary to support the execution of AWS Blu Age refa - 7. **How does AWS distribute new releases for AWS Blu Age Runtime?** + 7. **How does AWS distribute new releases for AWS Transform for mainframe Runtime?** @@ -92 +92 @@ An AWS Blu Age Runtime is necessary to support the execution of AWS Blu Age refa -The AWS Blu Age Runtime releases are accessible through the [Blu Age Toolbox](https://bluinsights.aws/docs/bluage-toolbox-introduction). See the [AWSBlu Age release notes](https://docs.aws.amazon.com/m2/latest/userguide/ba-release-notes.html). +The AWS Transform for mainframe Runtime releases are accessible through the [AWS Transform for mainframe Toolbox](https://bluinsights.aws/docs/bluage-toolbox-introduction). See the [AWS Transform for mainframe release notes](https://docs.aws.amazon.com/m2/latest/userguide/ba-release-notes.html). @@ -94 +94 @@ The AWS Blu Age Runtime releases are accessible through the [Blu Age Toolbox](ht - 8. **How often are new major and minor versions of AWS Blu Age runtime released?** + 8. **How often are new major and minor versions of AWS Transform for mainframe runtime released?** @@ -98 +98 @@ For more information, see [AWS Mainframe Modernization components lifecycle](htt - 9. **How does AWS provide support for AWS Blu Age Runtime?** + 9. **How does AWS provide support for AWS Transform for mainframe Runtime?** @@ -100 +100 @@ For more information, see [AWS Mainframe Modernization components lifecycle](htt -Support is provided through AWS Support, where issues are addressed by raising a ticket, and the standard SLA applies. For more information, see [AWS Mainframe Modernization components lifecycle](https://docs.aws.amazon.com/m2/latest/userguide/lifecycle-m2.html). +Support is provided through AWS Support for workloads running on AWS, where issues are addressed by raising a ticket, and the standard SLA applies. For more information, see [AWS Mainframe Modernization components lifecycle](https://docs.aws.amazon.com/m2/latest/userguide/lifecycle-m2.html). @@ -102 +102 @@ Support is provided through AWS Support, where issues are addressed by raising a - 10. **What does the AWS Mainframe Modernization AWS Blu Age Runtime entail?** + 10. **What does the AWS Mainframe Modernization AWS Transform for mainframe Runtime entail?** @@ -104 +104 @@ Support is provided through AWS Support, where issues are addressed by raising a -The AWS Blu Age Runtime includes toolbox libraries for accelerating modernization, facilitating cloud integrations, and improving code quality and maintainability. It also enables more modernization automation by facilitating transitions between legacy architectures and cloud architectures. The runtime provides support for handling legacy verbs and data structures memory representations using java idioms. It allows building modernized applications based on object-oriented programming techniques and able to reproduce legacy control flows. It modernizes legacy VSAM data sets or IMS hierarchical databases support using a relational database such as Amazon Aurora. It provides java replacements for legacy system utilities (IDCAMS, IEBGENER, DFSORT,etc), and legacy transaction management systems (CICS, IMS). It facilitates cloud integrations with caching in Amazon ElastiCache and support for AWS messaging solutions (SQS, Kinesis). +The AWS Transform for mainframe Runtime includes toolbox libraries for accelerating modernization, facilitating cloud integrations, and improving code quality and maintainability. It also enables more modernization automation by facilitating transitions between legacy architectures and cloud architectures. The runtime provides support for handling legacy verbs and data structures memory representations using java idioms. It allows building modernized applications based on object-oriented programming techniques and able to reproduce legacy control flows. It modernizes legacy VSAM data sets or IMS hierarchical databases support using a relational database such as Amazon Aurora. It provides java replacements for legacy system utilities (IDCAMS, IEBGENER, DFSORT,etc), and legacy transaction management systems (CICS, IMS). It facilitates cloud integrations with caching in Amazon ElastiCache and support for AWS messaging solutions (SQS, Kinesis). @@ -106 +106 @@ The AWS Blu Age Runtime includes toolbox libraries for accelerating modernizatio - 11. **Does AWS Blu Age Runtime support non-x86 computer architectures?** + 11. **Does AWS Transform for mainframe Runtime support non-x86 computer architectures?** @@ -108 +108 @@ The AWS Blu Age Runtime includes toolbox libraries for accelerating modernizatio -Currently, AWS Blu Age Runtime only support x86-based computer architectures and compute. AWS Blu Age Runtime doesn't support ARM-based and Graviton-based compute. +Currently, AWS Transform for mainframe Runtime only support x86-based computer architectures and compute. AWS Transform for mainframe Runtime doesn't support ARM-based and Graviton-based compute. @@ -110 +110 @@ Currently, AWS Blu Age Runtime only support x86-based computer architectures and - 12. **How can customers stay informed about AWS Blu Age Runtime versions, including notifications of new releases and access to version history and release notes?** + 12. **How can customers stay informed about AWS Transform for mainframe Runtime versions, including notifications of new releases and access to version history and release notes?** @@ -112 +112 @@ Currently, AWS Blu Age Runtime only support x86-based computer architectures and -New versions of AWS Blu Age Runtime are uploaded to our [official release page](https://docs.aws.amazon.com/m2/latest/userguide/ba-release-notes.html). We recommend checking this page regularly, ideally every 3 months, for the latest versions and updates. Regarding access to version history and release notes, availability depends on the end-of-life (EOL) date for each major version. For detailed information on EOL dates, version upgrade planning, and access to historical information, see [AWS Blu Age lifecycle](https://docs.aws.amazon.com/m2/latest/userguide/ba-lifecycle.html). +New versions of AWS Transform for mainframe Runtime are uploaded to our [official release page](https://docs.aws.amazon.com/m2/latest/userguide/ba-release-notes.html). We recommend checking this page regularly, ideally every 3 months, for the latest versions and updates. Regarding access to version history and release notes, availability depends on the end-of-life (EOL) date for each major version. For detailed information on EOL dates, version upgrade planning, and access to historical information, see [AWS Transform for mainframe lifecycle](https://docs.aws.amazon.com/m2/latest/userguide/ba-lifecycle.html). @@ -114 +114 @@ New versions of AWS Blu Age Runtime are uploaded to our [official release page]( - 13. **What are the main components of AWS Blu Age Runtime high-level architecture?** + 13. **What are the main components of AWS Transform for mainframe Runtime high-level architecture?** @@ -116 +116 @@ New versions of AWS Blu Age Runtime are uploaded to our [official release page]( -The AWS Blu Age Runtime architecture comprises two main component types. First are Java libraries (jar files) stored in a shared folder (accessible to the application server classloader) that provide legacy constructs and statements support. Second are web applications (war files) containing Spring-based applications that provide frameworks and services to modernized programs. The runtime also includes: a Programs Registry that collects all programs for invocation and cross-program calls and a Scripts Registry that collects all modernized jobs scripts. These components work together to provide a unified REST-based entry point and execution framework for modernized applications. The Runtime and the modernized application are deployed together in an application server (e.g. Tomcat). +The AWS Transform for mainframe Runtime architecture comprises two main component types. First are Java libraries (jar files) stored in a shared folder (accessible to the application server classloader) that provide legacy constructs and statements support. Second are web applications (war files) containing Spring-based applications that provide frameworks and services to modernized programs. The runtime also includes: a Programs Registry that collects all programs for invocation and cross-program calls and a Scripts Registry that collects all modernized jobs scripts. These components work together to provide a unified REST-based entry point and execution framework for modernized applications. The Runtime and the modernized application are deployed together in an application server (e.g. Tomcat). @@ -118 +118 @@ The AWS Blu Age Runtime architecture comprises two main component types. First a - 14. **How to configure the shared folder holding AWS Blu Age Runtime artifacts?** + 14. **How to configure the shared folder holding AWS Transform for mainframe Runtime artifacts?** @@ -120 +120 @@ The AWS Blu Age Runtime architecture comprises two main component types. First a -The AWS Blu Age Runtime artifacts (jars) must be gathered in a shared folder, accessible to the application server classloader. For a tomcat server, the configuration is made by modifying the regular configuration file named catalina.properties. For instance, if you created the shared folder as a folder named “shared”, in the tomcat folder, you will need to modify the common.loader entry in the catalina.properties to make the shared folder accessible to the tomcat classloader, as such: +The AWS Transform for mainframe Runtime artifacts (jars) must be gathered in a shared folder, accessible to the application server classloader. For a tomcat server, the configuration is made by modifying the regular configuration file named catalina.properties. For instance, if you created the shared folder as a folder named “shared”, in the tomcat folder, you will need to modify the common.loader entry in the catalina.properties to make the shared folder accessible to the tomcat classloader, as such: @@ -124 +124 @@ The AWS Blu Age Runtime artifacts (jars) must be gathered in a shared folder, ac - 15. **How does AWS Blu Age Runtime handle statelessness and session management?** + 15. **How does AWS Transform for mainframe Runtime handle statelessness and session management?** @@ -126 +126 @@ The AWS Blu Age Runtime artifacts (jars) must be gathered in a shared folder, ac -AWS Blu Age Runtime implements statelessness and session management through multiple mechanisms. For HTTP sessions, it uses cookie-based identification with external cache storage for user context. Sessions can be stored in various datastores including Amazon ElastiCache, Redis cluster, or in-memory maps. The statelessness design ensures that most non-transient states are stored externally in a common 'single source of truth', enabling high availability and horizontal scaling. This approach, combined with load balancing and shared sessions, allows distribution of user-facing dialog across multiple nodes. +AWS Transform for mainframe Runtime implements statelessness and session management through multiple mechanisms. For HTTP sessions, it uses cookie-based identification with external cache storage for user context. Sessions can be stored in various datastores including Amazon ElastiCache, Redis cluster, or in-memory maps. The statelessness design ensures that most non-transient states are stored externally in a common 'single source of truth', enabling high availability and horizontal scaling. This approach, combined with load balancing and shared sessions, allows distribution of user-facing dialog across multiple nodes. @@ -128 +128 @@ AWS Blu Age Runtime implements statelessness and session management through mult - 16. **What role do web applications play in the AWS Blu Age Runtime environment?** + 16. **What role do web applications play in the AWS Transform for mainframe Runtime environment?** @@ -130 +130 @@ AWS Blu Age Runtime implements statelessness and session management through mult -[Web applications in AWS Blu Age Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html#ba-shared-architecture-components) serve multiple key functions. They provide execution frameworks that reproduce legacy environments and transaction monitors (like JCL batches, CICS, IMS). They offer REST-based entry points through the `gapwalk-application.war` for triggering and controlling transactions, programs, and batches. Additionally, they provide emulation of OS-provided programs and specialized 'driver' programs that legacy applications depend on for accessing services like IMS DB or user dialogs through MFS. +[Web applications in AWS Transform for mainframe Runtime](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-architecture.html#ba-shared-architecture-components) serve multiple key functions. They provide execution frameworks that reproduce legacy environments and transaction monitors (like JCL batches, CICS, IMS). They offer REST-based entry points through the `gapwalk-application.war` for triggering and controlling transactions, programs, and batches. Additionally, they provide emulation of OS-provided programs and specialized 'driver' programs that legacy applications depend on for accessing services like IMS DB or user dialogs through MFS. @@ -132 +132 @@ AWS Blu Age Runtime implements statelessness and session management through mult - 17. **How are programs registered and managed in AWS Blu Age Runtime?** + 17. **How are programs registered and managed in AWS Transform for mainframe Runtime?** @@ -134 +134 @@ AWS Blu Age Runtime implements statelessness and session management through mult -Programs in AWS Blu Age Runtime are registered through a [ProgramRegistry system](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-run-call) that populates during server startup. Each program implements the [ Program](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-write) interface and is marked as a Spring component. Programs are registered using their identifiers, with multiple entries possible if a program has several identifiers. The registration process is automatic and logged in Tomcat logs. The [ProgramRegistry](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-run-call) enables other programs and scripts to locate and call registered programs, maintaining the modularity and interconnectivity of the modernized system. +Programs in AWS Transform for mainframe Runtime are registered through a [ProgramRegistry system](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-run-call) that populates during server startup. Each program implements the [ Program](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-write) interface and is marked as a Spring component. Programs are registered using their identifiers, with multiple entries possible if a program has several identifiers. The registration process is automatic and logged in Tomcat logs. The [ProgramRegistry](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html#ba-shared-structure-run-call) enables other programs and scripts to locate and call registered programs, maintaining the modularity and interconnectivity of the modernized system. @@ -136 +136 @@ Programs in AWS Blu Age Runtime are registered through a [ProgramRegistry system - 18. **How is configuration managed in AWS Blu Age Runtime applications?** + 18. **How is configuration managed in AWS Transform for mainframe Runtime applications?** @@ -138 +138 @@ Programs in AWS Blu Age Runtime are registered through a [ProgramRegistry system -Configuration in AWS Blu Age Runtime is managed through YAML files using Spring Boot framework capabilities. Two main configuration files are used: application-main.yml for framework configuration and `application-profile.yml` for client-specific options. The system follows Spring's precedence logic, allowing configuration overrides through various means. Additional configuration can be provided through JNDI for databases and command-line parameters, offering flexibility in configuration management. Loggers configuration is done using logback xml configuration files. +Configuration in AWS Transform for mainframe Runtime is managed through YAML files using Spring Boot framework capabilities. Two main configuration files are used: application-main.yml for framework configuration and `application-profile.yml` for client-specific options. The system follows Spring's precedence logic, allowing configuration overrides through various means. Additional configuration can be provided through JNDI for databases and command-line parameters, offering flexibility in configuration management. Loggers configuration is done using logback xml configuration files. @@ -140 +140 @@ Configuration in AWS Blu Age Runtime is managed through YAML files using Spring - 19. **What role do secrets managers play in the AWS Blu Age Runtime configuration?** + 19. **What role do secrets managers play in the AWS Transform for mainframe Runtime configuration?** @@ -142 +142 @@ Configuration in AWS Blu Age Runtime is managed through YAML files using Spring -Secrets managers in AWS Blu Age Runtime secure sensitive configuration data like database credentials and Redis cache passwords. They allow storage of critical data in AWS secrets and reference them in YAML configuration files. The system supports different types of secrets, including database secrets that automatically populate all relevant fields and single-password secrets for password-protected resources. This approach enhances security by keeping sensitive data separate from application configuration. +Secrets managers in AWS Transform for mainframe Runtime secure sensitive configuration data like database credentials and Redis cache passwords. They allow storage of critical data in AWS secrets and reference them in YAML configuration files. The system supports different types of secrets, including database secrets that automatically populate all relevant fields and single-password secrets for password-protected resources. This approach enhances security by keeping sensitive data separate from application configuration. @@ -144 +144 @@ Secrets managers in AWS Blu Age Runtime secure sensitive configuration data like - 20. **How can developers write their own programs compatible with AWS Blu Age Runtime?** + 20. **How can developers write their own programs compatible with AWS Transform for mainframe Runtime?** @@ -146 +146 @@ Secrets managers in AWS Blu Age Runtime secure sensitive configuration data like -Developers can create AWS Blu Age Runtime-compatible programs by implementing the Program interface and [following specific patterns](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html). The program must be declared as a Spring component, implement required methods, and be properly registered in the ProgramRegistry. Developers need to create companion context and configuration classes, handle program identifiers, and ensure proper integration with the Spring framework. The implementation should follow AWS Blu Age Runtime conventions for program structure and execution. +Developers can create AWS Transform for mainframe Runtime-compatible programs by implementing the Program interface and [following specific patterns](https://docs.aws.amazon.com/m2/latest/userguide/ba-shared-structure.html). The program must be declared as a Spring component, implement required methods, and be properly registered in the ProgramRegistry. Developers need to create companion context and configuration classes, handle program identifiers, and ensure proper integration with the Spring framework. The implementation should follow AWS Transform for mainframe Runtime conventions for program structure and execution. @@ -148 +148 @@ Developers can create AWS Blu Age Runtime-compatible programs by implementing th - 21. **How does AWS Blu Age Runtime handle program execution errors?** + 21. **How does AWS Transform for mainframe Runtime handle program execution errors?** @@ -150 +150 @@ Developers can create AWS Blu Age Runtime-compatible programs by implementing th -AWS Blu Age Runtime handles program execution errors through multiple mechanisms. For batch jobs, it captures execution status, exit codes, and detailed error information in the job execution details. Error handling includes specific exit codes (-1 for technical errors, -2 for service program failures) and detailed logging in Tomcat logs. The system can be configured to rollback transactions on runtime exceptions and provides options for error notification and recovery. Error details are accessible through REST endpoints for monitoring and troubleshooting. +AWS Transform for mainframe Runtime handles program execution errors through multiple mechanisms. For batch jobs, it captures execution status, exit codes, and detailed error information in the job execution details. Error handling includes specific exit codes (-1 for technical errors, -2 for service program failures) and detailed logging in Tomcat logs. The system can be configured to rollback transactions on runtime exceptions and provides options for error notification and recovery. Error details are accessible through REST endpoints for monitoring and troubleshooting. @@ -152 +152 @@ AWS Blu Age Runtime handles program execution errors through multiple mechanisms - 22. **What AWS Blu Age Runtime monitoring capabilities are available for batch jobs?** + 22. **What AWS Transform for mainframe Runtime monitoring capabilities are available for batch jobs?** @@ -154 +154 @@ AWS Blu Age Runtime handles program execution errors through multiple mechanisms -AWS Blu Age Runtime provides monitoring capabilities for batch jobs through various [endpoints](https://docs.aws.amazon.com/m2/latest/userguide/ba-endpoints-gapwalk.html#ba-endpoints-gapwalk-batch). It tracks job execution status, start/end times, execution mode, and detailed results. The system offers [endpoints](https://docs.aws.amazon.com/m2/latest/userguide/ba-endpoints-gapwalk.html#ba-endpoints-gapwalk-batch) for listing triggered scripts, retrieving job execution details, and monitoring currently running jobs. Metrics’ endpoints provide JVM statistics, session counts, and detailed batch execution metrics. The platform also supports pagination and time-based filtering of monitoring data. +AWS Transform for mainframe Runtime provides monitoring capabilities for batch jobs through various [endpoints](https://docs.aws.amazon.com/m2/latest/userguide/ba-endpoints-gapwalk.html#ba-endpoints-gapwalk-batch). It tracks job execution status, start/end times, execution mode, and detailed results. The system offers [endpoints](https://docs.aws.amazon.com/m2/latest/userguide/ba-endpoints-gapwalk.html#ba-endpoints-gapwalk-batch) for listing triggered scripts, retrieving job execution details, and monitoring currently running jobs. Metrics’ endpoints provide JVM statistics, session counts, and detailed batch execution metrics. The platform also supports pagination and time-based filtering of monitoring data. @@ -156 +156 @@ AWS Blu Age Runtime provides monitoring capabilities for batch jobs through vari - 23. **How are AWS Blu Age Runtime job execution statuses tracked and managed?** + 23. **How are AWS Transform for mainframe Runtime job execution statuses tracked and managed?** @@ -160 +160 @@ Job execution statuses are tracked through a comprehensive status system that in