Name: Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.2.
Uploaded: 2025-11-19T16:30:54.922Z
Duration: 37 min 8 s
Description: Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.2.

Transcript for "Rocket® Zena and Rocket® Enterprise Orchestrator 4.5.2.": Alright. I'm just gonna give it a little bit of time just to wait for some folks to join. K. I think I'm gonna get started with it. Welcome to the release webinar, of Xena Enterprise Orchestrator four five two. Just before we get started, just a few housekeeping slides. We will be recording today's session and distributing the links via email. The link will also be available on the community. Of course, we'd love to hear your questions and thoughts, so please pop them in the chat or q and a. There will also be poll questions throughout the session. So, just like you see on this screenshot, you'll see it in the same panel that the chat and the q and a is in. And lastly, we'll have a post event survey. If you'll please complete that, we'd really appreciate it. So lastly, we just have a rocket presentation disclaimer. And finally, I will pass it on to our, director of product management, Paul. Hey, everyone. Thank you for joining. It's release day, and we're there again with, four five two of Xena and Enterprise Orchestrator. So thank you for joining. I see really good attendance today, so thank you, marketing team. That's gone really well. Just a quick, just a quick update. The agenda is in front of you. We've got some really, really exciting, performance improvements, some new functionality, which is really interesting, and, as an update on our new integrations. I'll be turning I'll I'll be returning to that topic later on as, as well. 11 customers have contributed ideas and enhancements into release four five two. So when we get to those quick survey questions later, you'll see the value of that. And with that, I'm gonna hand over to, David Young, one of our senior engineering managers, to take us through the highlights of this new release. David. Thank you. Thank you, Paul. I'll share my screen here. I get to do the fun part here. Okay. Just a few things to to start out I'd I'd like to mention. We have made some changes to our SFTP monitor. We had a customer that wanted to be able to have up to, like, 1,200 SFTP monitors. And the way that we currently were handling that just it couldn't handle that volume. And anyway, we've made some changes in there with, connection pooling and thread pooling that's really increased that. And some tests that we've had up to 1,500 monitors out there going in with no kind of delays. So just a just a mention on that for the SFTP monitor. And we've also made some some changes to our enterprise server or what was used to be known as Micro Focus. We've made some in enhancements to that to support better throughput on our Micro Focus task there. So anyway, with that, I'm gonna get, I get to show you some new functionality here. I'm gonna start out with just showing you a couple of minor things that we've added. If we come here, first of all, to our system variables, I'm gonna go ahead and just create a new one. You have an option in here now to set, specify a script variable type. Now what this does is it's gonna behave just similar to as all system other very other system variables go, but this right here basically lets you set a language in here. And then when you're actually editing that script, now you have syntax highlighting on that, and then that easily can be used within other script tasks. You can insert that into there or even into a system command, you know, into an agent prescript or agent postscript. So if you have some common script that you wanna set up within a system variable, you can set that up now as a script system variable and have that syntax highlighting there. One other just quick note while we're looking at this right here, along with, agent side pre and post scripts, we have now added scheduler side pre and post scripts. And what that gives you is the ability to access more information on the scheduler side for massaging data and and information that you want to be part of that task that's being sent down to the agent. So it gives you a little bit more information and and, more objects and, you know, you have access to all the system variables there. You have access to the the process in there, the process variables there. So it it it'll help out on that side. Okay. The next thing just just a quick little thing here just I wanted to show. We've made a few enhancements to our delimited text field. Before, you know, we would just show these as comma delimited items, but now you can actually come in here. Let's say I wanted another one here, like one through 20, and then I can either press the comma or press the enter button and then let add as add it as a new item in that list. You can also use the ellipse button similar to before and come in here and add items. So, yeah, you have that ability both places. But it just makes it a little bit more visible on what things are as part of that delimited list. And you can easily remove those now. See, I don't want to have the this a b c in there. I can just click on that and then when I exit out, that'll be saved. So just a couple of fun little things there. Let me move on next. I'm gonna spend some time here in schemas and show you what new functionality we've added for you to be able to use these schemas. Those that have used broadcast tasks and broadcast processes, are probably familiar with these. It lets you run a number of, sub processes using, items defined for a particular schema. But we've taken that actually a little bit further now. I'm gonna show you three different examples, on on how you can use these now. I'm gonna start out quickly with this this common process data. Let's let's say in this example right here that you have some specific data that you always want to be part of processes, but you don't wanna have to define each of those as you go into that process. So if we come to the schema right here, I'll just take give you a quick look in here. I just added, you know, some test data here. But, now let's say that this data this these variables, I wanna be able to use a number of processes. What I can do now is I'll come back here to my folder, and let's come into this common process that I've got set up. I'm gonna come over here to variables. You'll you can see here it's a little hard to read. I I I've zoomed in a lot, so it's just a little bit easier for everybody to see. But if I double click on this right here, you can see that now within variables, I can set it to be of type schema. And then with type schema, now I can select the particular schema that I want used. And now I can either specify to use a specific instance, but in this case, all I wanna do is have that as a list of variables that I can use within the process, and I can set those here. Now what I can do is I can override those here, or if I don't override them, they'll use the default value that's set up within that schema. So if you have like some stuff at a high level that you always want just the same, you know, you can just define that within the schema itself, not overwrite it within the process. And then anytime you change that back at the schema, that will automatically be used when that process runs. But you also have the ability to here to override those. And then once you place these in here, those are accessible just like any other variable. You know, you can use them in the the data mapper or as you assign them to other task variables within scripts and so forth. I have just a simple example here of it being used within a data mapper. Let's just click on one of these data mapper items here. You can see here that to the process alias, I'm mapping whatever is in that application data schema variable that I defined, and I'm pulling out the emergency contact in it. So that you can just like I mentioned, you can use that just as you would any other variable. Okay. For my second example here, let me come back over to my schema. Let's tear. Let let's say you have different variable values, depending on which environment you're in. So if you're in QA, you have certain things that you want available, but those are different in your dev environment or in your production environment. So here I've just set up a simple schema that has just a few basics in it, but maybe these are different depending on which environment I'm running within. So to show you how you can use that now, let's come back to my folder. Not used to being zoomed in so far. Here within this folder right here, you can see that I've set up a instance of that schema that we just looked at for QA, one for QA, one for dev, and one for production. If I drill into one of those, you can see here that I've assigned some information for that within here, and then the same thing with all of the others. So let me come back again. I'm gonna just go into a process now now and show you how we can easily use that. I just set up a simple process here. Again, it's just it's just gonna be mapping some data later, but I'm gonna show you how that's actually used within the variable itself. So if we click on variables here, I've set up, in this case, a schema type variable again. I selected the environment data as my schema type. And in this case, I wanna use a specific schema instance. And what I wanna do here is not have that hard coded here, but have which instance I love what I want to use in another system variable called local environment. So in in my example, my local environment is set to QA. So what will happen when this process runs is, first of all, this token will be resolved, and in my case, it's gonna be resolved to QA. And then at that point, this the process is gonna say, okay. They wanna use that particular schema instance within this process. And so my previous example, we just had the fields, directly there, and you could override those. In this case, it's going to pull those values from that schema instance that I have out there. In my QA environment, I can use any of those variables that I set up in that schema instance. So if I export this and import it into another system, all I have to change is what environment I'm pointing to in the local environment system variable, and then that would automatically make it so that's available with any processes that are using it. Okay. And then for my last example, I'm gonna show you another one quick here. I have another schema that I've set up here called department information. And, you know, it just in my case, again, just some dummy data. But you can have, you know, some specific information in here, you know, depending on your department. And then what I can do now let's come to another come back here first. First of all, I just I set up just some simple examples here, department a, department b, and department c. But what I can do now is I'm gonna just show you an example within a process, I have this thing called Update accounts event. Oh, I'm sorry. I want to go into the process. Update. Let me see. Update accounts process. I'm gonna click over my variables again, double click on this. In this case, I've set up my process variable variable to be a type schema, but using the department information schema. And I want it to use a specific schema instance again. And here I just have some default one placed in here, but I'm gonna show you now how that can be used within event here. So if I come over to this event, I've set it up just to use a, a simple event I set up which sends the department name. But anyway, so this is the name of the event. If I come over to variables, you can see now at the variable level that I've got that department schema that's available. What I'm doing now is I'm taking from this user event in which I define the department, I'm taking the event attribute department name that I pass in that, and that's gonna determine now which schema instance will be used within this process and give them now access to any information about that specific department. So if you have, you know, certain events that occur through a day and you have some generic, processes out there that that can be used, you know, just for different data given to that, Now you have that ability to to come in through this right here, have some event determine which, schema instance will be used, and then that process will just use that information as it runs the different tasks and other items within that process. So just to give you a quick example here, let's let me show you just a quick example on this one right here. Come back to my folder here. So I'm gonna fire this off with my user event. And when I fire it off, I have it prompting me for which department to specify. So let me go ahead and just run this. In this case, I'm gonna say I want it to use the department a. I'll click okay here. We come over to my run time side, I'll click on processes. K. We can see that that process went active. Now in there, I was mapping that department name to the alias. So you can see now because I told it to use the department a schema instance, it was it mapped from that instance into the alias, the name of that department. And you can see that there on the alias. So again, you know, like in one in this case, I'm just showing one piece of data, but any anything else that's included as part of that schema instant is instance is available within that process. Okay. Let me see. Another quick thing I'm just gonna show you. I think that's everything I have to show on how you can use these schemas now within Xena. Does it I don't know if there's any questions that wanna anybody wants to bring up on these. You're welcome to bring those up right now if you if you would like to. Yeah. David, there's one from Pat. Is there a role for scheme management, I, view, change, etcetera? Yes. The the schemas there's there is a particular role that's required to set up a specific schema, and so somebody needs the right to be able to do that. And then there is a right for whether or not you can actually create schema instances. So if that person has a right, just like any other definition, schema instances are defined within, definition folders. Depending on what you have access to there, those are the items that will show up. Okay. Thank you. And I have another question from Omar. I have three test environments within a single Xena instance, dev test and stage. And then the I can't see the rest of the question. That's all within the same environment, then then you're kind of, at that point, treating it more kind of like I was showing the department example. You know, if if you wanted to use specific variables dependent on, you know, a schema instance out there, you just need to make sure that you set that, that variable that was defined within the process to that specific instance. In in in my example, I was treating it as if there was three different environments, and then I had a, a system variable that was defining which one this environment was using. But if you but again, like like you mentioned there, if you're doing all three within the same environment, then you'd have to specify that with you know, as you run each process, which which set you wanna use, which which variable. set Hey, here you. wanna use. Let let me let me add to that. Thanks, Olivia. I didn't realize there was a read me button. I'm I'm we're getting used to this new software. So, following on, Omar says, I need to to manage system variables across these environments. What are the best practices for handling this type of situation? Also, I'm curious about how I can store secrets in global variables while keeping them masked. So I think you covered some of that. Yeah. May maybe take that one point at a time. Maybe just mention the first one again to me, Paul. So what are the best practices how do you manage variables type of situation? I'm sorry. Say that again, Paul, one more time. What are the best practices for handling this type of situation? So it's, needing to manage system variables across the three environments. Well, it's, you know, it's really just like any other data that you have and and and as you need to move those across, you know, those can be moved through, packages or through exporting and importing to files or direct imports. You you know, you you just have to ask people make changes to those and they need to be propagated to their systems. Those just need to be moved from one system to the other. Okay. Cool. And the second part of Emma's question was storing secrets in global variables. Yeah. That's that's a good question. That's something that maybe we need to discuss, Paul, and and come up with an answer. Nothing comes to mind on on that one right now. Okay. Thank you for your question. A good one. It stumped us. We'll we'll, take that offline and get back to you. Spencer asked another one. It's hard to see, but there is a read oh, you're helping me navigate the software. Thank you, Spencer. Alright. We're we're done with the questions, David. Let's let's continue. Okay. Great. Thank you. Okay. The the last item I'm gonna show here is just a just a couple of enhancements that have made been made to our reporting system. Let me come back here. Let's just go into a definition report here. In the queries, as you set up a new query and you set up a filter, we just added some extra options here in the condition area for being able to check. Let me actually change this to a string. Just to make things easier here, we've added both an empty and a not empty item right here just so that you have those specifically to check. So rather than checking against blank blank screens, you can actually put those in there. I I think that's the last item, Paul, unless there's anything more that you want me to cover. Any more questions? If not, then I think we're Okay. I will stop sharing on my side. good. Okay. Thank you. Thank you, David. We'll have, a poll question shortly, but I'm just gonna, give you an update on integrations, and then we'll have a q and a session at the end. Okay. So let me update on, let me turn my camera back on. Integrations. Okay. So, yeah, I come across a survey recently that said that, organizations were, adopting cloud first policy. You know, so about about about 55% of organizations. And when you get to the enterprise level, it's more like 94%. And this is certainly something that we see in the interactions we have with with many of our customers and prospects that they're moving workload to the cloud. And so something like about three years ago, it actually preceded my time as product manager for this tool for this product set. We started an initiative to to really hone in on that messaging from from from customers and prospects and start developing, many more of the cloud integrations. The r and d team have done a cracking job. So this slide is focusing on what we've delivered over the last two or three releases. You'll see down the bottom of, the Azure one column, for example, it says four five two. So we're delivering that as part of this release. And then on the next slide, we're only we're we're identifying those that we have planned. Now many many of these have already been committed to April, and the April release is coming out, let me just pick up my notes, 03/21/2026. That's the planned, date anyway. And we normally pretty good on our planned dates. So you can see we're focusing very much on Azure, AWS, and GCP. If there are any other integrations, maybe non cloud related, then databases, applications, things like that, please let us know. Please, make make sure you you you, either email me directly or open an enhancement request for it. We as I said at the at the start, we we got, enhancement requests from 11 customers, included in four five two, and we do like to be driven by by what our customers need. So that's where we're planning with the cloud integrations, and it's it's mapping nicely with a lot of the calls and conversations that we're having. So with that, I'm gonna move on to our first poll question. we continue to pull, let me go back. David. Yes. Sure. I was gonna ask Paul. Yeah. And maybe before we continue there, can I can I point out just one specific, new integration that we have there? Listed. I I just wanted to maybe bring out the we have a RESTful API dependency monitor that we've placed out there now. What it allows you to do is, you know, say you have a task where you wanna call a RESTful API that's gonna start some job or process. And, anyway, you know, you you get back that response immediately within Xena, and now you want it to wait until that it's it's actually completed, something's completed on that other side. Well, with the RESTful API dependency monitor, you can basically, within that monitor, give it a a RESTful API call where it can be check the status of that that job or task that was instantiated in some other system. And then it waits to get a particular response back in that to to let it continue running from that point. So, you know, so basically, it, you know, it gives you the ability to have something started in one restful API and then have it wait until it's completed using this this webs the the restful web service dependency. I just wanted to to point that one out, kind of an interesting one. It is. Great. Thank you, David. Okay. Greta, should we move on to the poll? While we're before I get into the poll, we had one question. Does the restful API trigger look for codes, or can it pass looking for keywords? It it lets you set up a list of keywords to look for. And so and and you can set up the order for that. So you you basically, there's a list of items that you set up in there and say, if it contains this, I want it to be met, or if it contains this, I want it to not be met. So, you know, depending on the order, whichever one it hits first, it'll either set it to met or not met. And if it doesn't. match any of them, it'll just be in a state of not met. So, yeah, it it gives you quite a bit of, ways, you know, to to to check for that response. Okay. Cool. So I, I probably messed that up. Sorry, folks. The first poll question was what cloud integration should we prioritize? I actually see things have moved along, and I think we've got answers on that now. So, I can see actually, that's that's amazing. It's actually an almost exact split between, all three, AWS, Azure, and GCP. So I see oh, no. Some other changes. So AWS and Azure are the seems to be the most popular ones. Okay. Thank you. So I think, I think we've done on poll one. Poll two is, we're interested to know where you are deploying automation next. So think about, maybe upcoming projects. Are you put pushing automation into a different area where perhaps you don't have it, focused at the moment? That would be really interesting for us, a new application, a new database, new cloud integrations. That that would be the kind of thing that we're looking for here. Or maybe you're gonna, planning to to start driving your data pipelines with, with enterprise orchestrator. So that would be interesting to know. Okay. I'll just pause a second while we, collect some input on that. And just real quick, I can see cloud automation's getting some high votes. Disaster recovery. Oh, that's an interesting one. Okay. Very good. Thank you for that. Okay. We'll continue to, to monitor those as they come in. And I think, oh, there's another update. So So what else are we getting coming in? More on the cloud automation, more votes for disaster recovery, but also DevOps pipelines and virtual services is catching up as well. Great. Thank you. Great information for us. Thank you very much. Appreciate it. Okay. Let's move on to q and a. So is this where we open up, the microphones, Greta? Be before we swap over to q and a, Paul, Yep. there is one item that I missed that I just would like to bring up here really quick. It was I I just missed it as I was going down my list here. Okay. Do you wanna share? One other piece I'm I'll just I'm just gonna talk through this one. K. It it's fairly straightforward. We we had a customer that came to us and then mentioned that on the last day of the month, they have a file that comes in. So they they wanted to have a directory monitor that would only run on that specific day so that it's not out there the other twenty nine days of the month out there running, not doing anything. So what we've done is on all of our event monitors, you now have the ability to specify a calendar. And if you specify a calendar, that event monitor will only run down on the agent during days that are part of that calendar. So, like, in the example that I mentioned, they specified a, last day of the month calendar in that event monitor, and then it was only running on the last day of the month for them. So again, that's that's available in all of our event monitors. So if there's only specific days, you know, that it needs to run, you can, set up a calendar for that and then assign that calendar to that event monitor. That's, that's, I think, is everything with that. So with that, Paul, yeah, we can open it up to q. and a now. you, David. I'm reliably informed that we are any questions, please add add them into the q and a area. That would be great. Oh, there's another chat. Event monitor calendar is a useful tool. Thank you, Pat. Good information. I like that. Just gonna pause for a minute and see if there's any questions coming into the q and a. If not, we'll, we'll continue. We've covered most of the content that we wanted to update you with today. But I I do have one quick advert if, if we have time. No other questions coming in. David, you've obviously done a brilliant job there, and I think we should move on. So lastly from me, a a really quick advert. It's not a topic a detailed topic for today, but I just wanted to make sure that we covered this. AI predictive pulse empowers organizations to proactively prevent SLA breaches, reduce downtime, and optimize operations through real time predictive analytics and AI driven insights. AI predictive pulse is an add on, a SaaS based add on to Xena EO and Zeek as well. And it and it does all that good stuff by combining multilayered intelligence with machine learning, which enables faster decisions, cost savings, and improve business resilience. If you haven't had a chance to talk to your sales representatives about this solution or your presales engineers, please reach out. You'll you'll really be interested to find what it can do for your business. And it can be proactive as well. So it can take actions once it's trained, once it's the model is developed. And it's running at 45 sites around the world. The software is running at 45 or more sites around the world. So it's battle hardened. It's proven. And we could also incorporate information, job information from other enterprise schedulers as well. So it really can give you that that total business operations view umbrella over all of your your business processes and, and scheduling activity. So just a really quick teaser for today. And with that, Olivier, I'll pass it back to you. I don't think we have any more questions. So, that's I think, I think that's a wrap. I was just gonna mention just on your AI principles, if you, join the community, the Greta put the link in the chat. We just posted an operations based demo if you'd like to check that out. It's a pretty fifteen minute short demo. So just with that being said, I, I'm happy to see you there and continue the conversation on the forum. And if you have any last minute questions, feel free to pop those in the q and a, and we'll get back to you. And lastly, I believe Greta opened up the post event survey. If you'd like to fill that out, we'd love to hear your thoughts about our the webinar, and to see what we can deliver for next time. So you. with that being said, there's no other, questions. everyone. Thank you so much for joining, on our release day. Have a great rest of your day.