[MUSIC] Hello and welcome to this course I'm Sophie Green and I'm a developer in the IBM CICS team based in software development lab in Hursley, UK. Over this course began to explain why CICS is perfect for powering the next generation of enterprise applications and how you can help to build them. If you haven't already, read, strongly recommend that you take both the instructions to CICS video course as well as the introduction to COBOL video course. As these will really help to expand some of the key concepts that we're going to be building upon. It would also help if you have a basic understanding of Java, but don't be scared off if you don't. During the course, there's going to be a mixture of lecture style sessions as well as labs that you can use to really help cement your knowledge. We can also provide you with the provisioned environment for you to use during the labs if needed. By the end of this course, you should understand why IBM CICS has been entrusted core of enterprise applications and my three years of innovation, this trust is really maintained. You will experience Brighton updating and running CICS applications. As well as the new APIs capabilities and functions that allow you to modernize these applications to run as part of a hybrid cloud application. Sound interesting? Of course, it does. So let's get started. I should already know CICS is a mix language application server that runs on IBM Z. Over the 50 years since CICS was introduced in 1969. Enterprises abuse the qualities of service that CICS provides to allow them to create high throughput, secure transactional applications than freely powered their business. A CRT landscape is involved, so have CICS to allow these applications to integrate with new platforms and therefore still provide value to the rest of the business. Because of this capability, a lot of businesses still rely on CICS to power their core applications. When CICS debuted, the title and state was primarily dominated by batch processing. Anytime I record is updated, for example a bank account or customer details, these changes will be batched together with other changes, and then applied sequentially was the main records. CICS introduce the ability to update that record immediately without the need for batch window to run. CICS would handle all of the transactionality of the processing without the application programmer having to worry about, for example, what to do if the record you want to update is locked. After landscape moved to embrace online transactions, CICS introduce capabilities to support different programming styles, such as conversational and pseudo conversation. These allowed throughput increase as more people could update records at the same time. Today the cloud is dramatically changed IT landscape again. Being able to make use of services, functions and platforms as a service allows organizations to create amazing digital experiences for their clients. However, the heart of these experiences is still the cool applications hosted by CICS. Since 89% of enterprises predicts needed to harness multiple public and private or on premise clouds, we call this unset the hybrid multi-cloud. Migrations, since the hybrid cloud requires clients to look at their existing assets and decide how they can migrate into the cloud, and there are three possible methods to achieve this. The first and probably the simplest is to maintain the status quo or just keep the existing applications welcome. Although, this doesn't incur any extra costs or introducing you risk, the application might then full behind technologically. This might eventually incur problems as the business tries to embed these applications into new digital experiences. The second method is to migrate all of their applications to the cloud as cloud native applications. This is not only a high risk approach as there's no guarantee that the migrated application or have the same performance, security, or transactional capabilities as the is replacing. It is also quite an expensive approach. Not only is the cost of the migration likely to be higher, but you also have to maintain the existing applications until that migration is complete. Less on caring further costs. Final method, and perhaps best, is to modernize the applications that you already have, allowing them to integrate with cloud native applications. This modernization could be achieved either by constructing APIs that allow new cloud native applications to connect to your existing assets. Rewriting parts of your application in newer languages, and then hosting them back on CICS or by using CICS capabilities to extend your applications to provide new capabilities and functions. And this is exactly the type of modernization that we're going to be focusing on during this course. What we're going to do is, we're going to take a traditional example application, show you how it works. And then, through the course we're going to extend it, rewrite bits of it, and then API enable it. All done, so we will explain how CICS applications make use of continuous integration and continuous delivery till I you to deliver, test and deploy code into CICS easily and with quality. But we have to stop the most famous example ever, Hello world. It would be really rude not to. If you did the previous COBOL course, you have written a small program that did nothing but write, Hello World. So let's do the same, but for CICS. Here is the Cobol batch program that's created at the beginning of the cobalt course. As we read explained, kicks provides application programming interfaces or APIs to programs to allow them to interact with resources. So here's the same code, but using CICS APIs to write the same string to the terminal. Here it will look at the identification division of archival program. And here we can see that our program is called Hello, and then it's in the procedure division that the interesting stuff happens. We have two API quincy. One is by the string Hello World, the terminal that started the program, and then one to let CICS know that this program has completed. Obviously, the applications that keeps customers use, it going to be a lot more complex than this. They're going to interact with a lot more than just a console, but the basic building blocks are the same. Take what you learned from the COBOL course and in the CICS APIs to allow you to write enterprise applications. And that is what customers have been doing for over 50 years. So let's have a look at one of the applications next. [MUSIC]
