2244 Modernizing ACE Applications to work in container environments.pdf

《2244 Modernizing ACE Applications to work in container environments.pdf》由會員分享，可在線閱讀，更多相關《2244 Modernizing ACE Applications to work in container environments.pdf（26頁珍藏版）》請在三個皮匠報告上搜索。

1、Session 2244Modernizing ACE Applications for Container environmentsShane WarehamUnited Airlines,Principal DeveloperNaveen AnagantiUnited Airlines,Principal DeveloperPaul FaulknerIBM Expert Labs,Technical Account ManagerCustomizeCloud Modernization What is it?InfrastructureApplicationAutomateRe-Archi

2、tectureAssessmentRe-EngineerCompile&BuildContinuous IntegrationTestBuildContinuous DeliveryDeployConfigurationsApplicationCloudClusterPlatformScalingHigh AvailabilityKubernetesACE OperatorConfigurationsBuild&DeployIBM App Connect Kubernetes OPERATORIntegration Server/RuntimeConfigurationDashboardCus

3、tom Resources owned by the App Connect OperatorApp Connect OperatorCertified ContainerIntegration Server/RuntimeIntegrationCustom ResourceDeploys containerized App Connect Enterprise and manages their associated environment-specific configurationsDeploys App Connect Enterprise DashboardModernizing A

4、pplication CodeTransformation AdvisorModernizing Application CodeTransformation AdvisorModernizing Application CodeTransformation AdvisorModernizing Application CodeHands on peer reviewsReviewing code with a code walk-thru is the most effective meansGoal is to have an immutable deployed artifact so

5、UDPs no longer have any benefit,but we still need a way to provide runtime properties-use Policy filesNew we have ability to create End Point policy files for HTTP Request to use a Policy(show this and identify version it was available in)Aggregation migrate to Group Nodes-talk about the issue with

6、Aggregation using internal queues to store state.Externalize ParametersWHAT:AVOID BAR file overridesWHY:We want a consistent deployment artifact throughout the deployment lifecycle to ensure consistency and reduce testing impactHOW:Use Policies for external parameters LegacyModernizedMQ ConnectionsM

7、Q Endpoint Policy HTTP End PointsHTTP Endpoint PolicyUser Defined PropertiesUser Defined PolicyACE Operator-Common ConfigurationsTypeUseBarAuthProvide credentials to access an external repository for application deployable resourcesGenericProvide a file directory of files accessible from within the

8、containerKeystoreHolds configurations that reference a keystore,can be used for external sources such as MQ,HTTPODBC.iniDatabase connectivityPolicyProjectConfigurations that contain policies(within a policy project)to control the behavior of the message flows and message flow nodes at run time.serve

9、r.conf.yamlConfigurations that use the server.conf.yamlfile to configure the operation of the integration server or integration runtime and its associated resourcessetDBParmsConfigurations that contain mqsisetdbparmscommands to run when the integration server or integration runtime is deployed.ACE O

10、perator Dashboard DeploysDeploying What happens?CI/CD PIPELINECustom Resource DefinitionPODContainerApplWorker Node 02Worker Node 01deploysdeploysbuildsDashboard CreationACE Operator IntegrationServerMeta Info(Name and Namespace)Container size(CPU and Memory)ACE VersionScaling(number of Replicas)BAR

11、 Location(internal or external repository)List of ConfigurationsACE Operator ConfigurationMeta Info(Name and Namespace)context base64 encodedConfiguration TypeClusterScaling&High AvailabilityWorker Node 01Worker Node 02Worker Node 03Continuous Availability-Deploying ChangesBAR RepositoryapplX.barapp

12、lY.bar.Configuration CRsserver.conf.yamltruststorepolicyContinuous Availability-Deploying ChangesWorker Node 01CR Specification Change HappensBAR,Configuration,Resource Specification.Automating the DeploymentAutomating the DeploymentThe United Airlines ProcessAutomating with triggers,pipelines,and t

13、he App Connect OperatorWhere we wereThe move to OperatorsPipelines for Common ConfigurationsSome configurations,while environment specific,are common to multiple applications.Among these are the MQ Policy folders and keystoresThe MQ Policy folder must be zipped into a single file,then encoded as bas

14、e 64 to be deployed as a configuration itemThe keystores will hold the certificates to connect to various external resources.These files are built on the fly in the pipeline process and encoded to base 64 before they are deployed as configurations Uses a K8s integrationruntime manifest Which is appl

15、ied to the namespace in the cluster Along with the version of ACE(in this case the latest fix pack of ACE 12.0)The BAR file is pulled from the artifact repository where its kept The configurations that the app will use are gathered from the namespace and injected into the containerThe IntegrationRun

16、time manifest for BAR file deployments Types of configurations User Defined Policies MQ Policies Endpoint Policies MQ Keystore Endpoint Keystore Server Conf YAML Deployed independently of the application Referenced by the application in the integrationruntime manifestJIT Creation of Configuration Ma

17、nifestsInsert the base 64 encoded string into the contentsCreate a configuration manifest fileEncode file in base 64 into a stringZIP folders into single filesHow the Operator puts it all togetherThe App Connect Operator handles the integrationruntime manifest file for deployment.It will get a copy

18、the ACE container image and add the BAR file referenced in the manifestThe operator will then pull in the configurations referenced in the manifest into the container.These configuration items will be decoded,and unzipped if needed,into the correct folders in the container.The container will then be

19、 started and the BAR file(s)initialized.Notices and disclaimers 2023 International Business Machines Corporation.All rights reserved.This document is distributed“as is”without any warranty,either express or implied.In no event shall IBM be liable for any damage arising from the use of this informati

20、on,including but not limited to,loss of data,business interruption,loss of profit or loss of opportunity.Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved.Actual performance,cost,savings or other results in other ope

21、rating environments may vary.Workshops,sessions and associated materials may have been prepared by independent session speakers,and do not necessarily reflect the views of IBM.Not all offerings are available in every country in which IBM operates.Any statements regarding IBMs future direction,intent

22、 or product plans are subject to change or withdrawal without notice.IBM,the IBM logo,and are trademarks of International Business Machines Corporation,registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trade

23、marks is available on the Web at“Copyright and trademark information”at: comments made in this presentation may be characterized as forward looking under the Private Securities Litigation Reform Act of 1995.Forward-looking statements are based on the companys current assumptions regarding future bus

24、iness and financial performance.Those statements by their nature address matters that are uncertain to different degrees and involve a number of factors that could cause actual results to differ materially.Additional information concerning these factors is contained in the Companys filings with the

25、SEC.Copies are available from the SEC,from the IBM website,or from IBM Investor Relations.Any forward-looking statement made during this presentation speaks only as of the date on which it is made.The company assumes no obligation to update or revise any forward-looking statements except as required by law;these charts and the associated remarks and comments are integrally related and are intended to be presented and understood together.26IBM TechXchange/2023 IBM Corporation