As the leader in deployment automation, Serena is a proud sponsor of the Jenkins User Conference 2015 World Tour. Come visit us at our booth and meet our experts in DevOps, CI/CD and enterprise release management.
Network Learn Explore @ the largest gathering of Continuous Integration and Continuous Delivery experts on the planet.
Want to tap the collective knowledge of a vibrant community of CI/CD practitioners? How aboutRead More
DevOps turned five last October, and while five years seems like a long time in terms of the technology adoption lifecycle, DevOps and Continuous Delivery still seem perched on the Enterprise IT chasm. The Pragmatists get it. They are under pressure from the business to deliver business value faster, better and more cheaply and the Visionaries and Early Adopters have proven that Continuous Delivery fits the bill.
The problem is that Enterprise IT canRead More
Greg Hughes talked about the need to “Move Fast Without Breaking Things” and his first love … a 128k RAM, twin 320kb floppy, 32lb “portable” computer. He drove home the critical need of modern organizations to create an infrastructure environment that supports dev teamsRead More
We were joined by one of our early adopters of the innovative Dimensions CM 14 release, Carmelette Benson of Health Care Service Corporation. The VUG was treated to an exceptional upgrade story that engaged the free Upgrade Lab to advance their planning and readiness, and worked collaboratively withRead More
Well! We’re all set to go! We have a great agenda, a fantastic lineup of speakers and some fun activities planned. If you haven’t registered yet there is still time – you can register here.
Let’s take a quick tour of the highlights …
Once the developer checks in a change, how long does it take your organization to deliver it to the customer? The path to production can take many turns, have many dips, and fall short in terms of quality and expectations. IT organizations struggle with major process and toolchain gaps between develop, build, deploy, and release. Come join us at the December Serena DevOps Drive-in as JulianRead More
How do you become a high performance IT organization? Earlier in the year we had Glenn O’Donnell of Forrester on our Serena DevOps Drive-in webcast to answer this question. Glenn outlined the fact that we are in the beginning of an IT industrial revolution: IT is currently too slow, has poor quality and customers don’t trust IT. This current state hasRead More
If you are planning on coming to xChange I want to remind you that the early bird pricing expires on December 31st. Right now you can save $200 off the registration fee.
See you in Washington DC in March!Read More
It is so easy to open Composer, make a "little" change and click Quick Deploy. But, is a Quick Deploy sometimes too quick? Have you ever waited patiently for the "Deployment Completed" message only to realize that you deployed to production instead of staging? Or, maybe you didn't realize what happened until users started to call about sudden strange behavior... Don't feel bad. It's happened to a lot of administrators. We hear from customers all the time who have deployed something to production by mistake and now need to rollback.
Here we will discuss how to prevent a quick 2 minute change from becoming a long 2 hour recovery exercise.
Today is my 15 year anniversary with Serena. WOW! A lot has changed during this time.
Before joining Serena I was a customer. (actually it was Merant; Serena acquired Merant in 2004). I worked for a defense contractor in the Washington DC area managing the software CM department. My very first task with this company was to move them off their outgrown, homegrown system to a COTS system.
Did I mention that I knew diddly squat about proper CM much less anything about overseeing the department? But having worked as a developer for another large defense contractor, I had firsthand experience of what life was like when things went wrong. Spent way too many late nights tracking down the elusive change that somehow didn’t make it into production.
So I used that experience as a guide into this new adventurous dark side—Change and Configuration Management. I remember the developers at my new job always got quiet whenever I entered their space. Like I was some evil person. In fact, one of the developers said to me, “you’re here to make my life harder.” Being the sweet, gentle person that I am (cough! cough!), I replied “just the opposite, I was hired to make your life easier.” I was convinced that I could convince him to see the value of good CM practices. Yea, right.
So I took a two pronged approach. First and most importantly, I involved the developers in the evaluation process. I brought in the top three market leaders and asked the developers to help me in the selection. Dimensions came out as the winner and so began my journey with Dimensions CM.
Oh, and the second prong…..I joined their softball team. Figured I would show them that folks in the CM department are human beings too. We’re not evil, control freaks. Okay, maybe just not evil. :-)
Oh, life was simple then. I didn’t own a cell phone. Work actually had to page me after working hours. I know some of you reading this remember those days.
Here are some simple ways to customize the Serena Request Center by editing the wrapper.htm file.
In this blog, I'll be adding:
The flexibility to customize ZMF to meet your user's requirements is one of the great advantages of ZMF. This flexibility also introduces additional complexity as you upgrade ZMF from release to release. Customer feedback tells us that forward fitting your customizations to a new ZMF release is a significant part of every upgrade project. At xChange 2015, we hosted a 'best practices' session on this topic which received positive feedback on the recommendation to 'take the vanilla challenge'. For those unfamiliar with my use of the term 'vanilla', it means 'as delivered' or 'out of the box'. The challenge for you, is to to investigate your customizations and eliminate those that are unnecessary.
So, what are the items to consider as you attempt to minimize your customizations?
This video demonstrates a feature in Composer that makes it easy to reuse your forms, both within an application and between them. When you copy a form and its underlying table changes, the fields on the form may no longer be valid. The form copy mechanism maps fields with identical names and types, and an addition feature lets you change the table field associated with any control on the form.
If you enjoyed reading this blog entry, please subscribe to my blog by clicking the 'subscribe to updates from author' link below.
For Serena Business Manager (SBM) versions 10.1.5.x and earlier, the provided and only supported application server was Red Hat JBoss. Due to changing market conditions, Serena Software has decided to change the provided Application Server from Red Hat JBoss to Apache Tomcat.
Currently, as an application server, version 4.0.5 of JBoss is distributed with SBM. The version of Tomcat on which this version of JBoss is based is Tomcat version 5.5. This version of Tomcat has reached its end-of-life, so a newer version of an application server needs to be distributed with SBM. Because a new version had to be included, analysis was done to determine if upgrading JBoss was the right direction or whether an alternative would provide more value. During this research, Serena received feedback from many customers who preferred the community version of Tomcat over the forked version found in JBoss. It also enabled a more simplified distribution as some JBoss capabilities were not exercised by SBM. Thus, Serena has decided to embed the community version of Tomcat directly rather than JBoss with the next major release of SBM. A newer version of Tomcat will also benefit customers because the technology has added improvements in garbage collection, JSP parsing, performance and scalability. And finally, the community is active on newer versions; discovering, reporting, analyzing and correcting defects in a timely manner.
Occasionally a server configuration problem can prevent communication between the Application Engine server and the Common Services server, resulting in a failure to run the Request Center and Work Center products. This article covers the steps to diagnose the problem or at least gather more information.
Dimensions Build includes a notification facility that enables you to send email messages containing information about build events. For example, you can notify users when a build is completed or when a build area is updated.
This post provides quick instructions on how to create build (email) notification templates for Dimensions CM Build. Templates are useful when you want to re-use the same subject and message in multiple notification events.
The overall steps are:
I commonly hear the request to have an approval step in a workflow that is going to be variable. The other catch to this request is that the approvers change somewhat frequently, so there is a desire to not to have to make an administrative change each time the approver is going to change.
The best way to implement this is using an auxiliary table that will contain the user field with the defined approver and add permissions for a specified group of people to be able to update the auxiliary table records.
The challenge becomes, how do I get that approver field value copied to my workflow. Before the days of orchestrations, we commonly would use TeamScript/AppScript for this.
Amongst the most common type of issues reported to Serena Support’s ZMF team are problems related to ChangeMan ZMF security profiles. It is reasonably common for us to discuss “Dave being unable to see or select the admin option” or “Heidi not being allowed to create a package in application TOGA”.
So, how do we go about researching such a problem and can customers perform any self-diagnosis of such issues? Obviously the answer to the latter is ‘yes’ or this would be a very short blog entry. So, let’s use an example and work through the diagnosis process.
In SBM 10.1.5, we've added a powerful and flexible new way to configure the REST Grid widget.
In earlier releases, to configure the REST Grid widget you would enter an URL to the REST service. Composer called that service, obtained a result and used it to determine the expected structure of the REST data so it could be used for mapping to other controls. However, this process failed in a number of circumstances. For example, the Composer user might not have permission to access the REST service, or the service might not always return all the data elements that might occur in production use.
Back in SBM 10.1.3, we included a new feature to call REST web services with orchestrations. The RESTCaller is included in the Composer interface after you upgrade. You simply drag it onto your orchestration flow diagram and start to configure it the same way you do SOAP based web service calls. Since this is essentially a wrapper, there is a little bit of translation that you will have to do. There are two resources that you will want to reference.
When preparing for our ZMF 8.1 upgrade we have obviously all checked the Serena Support site – OEM Software Compatibility information here (you need to be logged into the Support website to access this link). And from this we understand that z/OS 1.12 is the minimum supported operating system.
However, we all know that we can always fire up ZMF on an earlier z/OS level and it will just about always work, right? Well, no, that is not the case with ZMF 8.1.
If you are part of the ChangeMan ZMF community, you may have received the ChangeMan ZMF Product Survey which went out in February of this year. If you were at xChange 2015, or if you’ve been on the last couple of Mainframe VUGs (Virtual User Groups), you have heard Mark Levy and I mention the survey.
During the kickoff session of the Mainframe track at xChange, among other topics such as the product roadmap, product futures and initiatives within R&D, I presented a glimpse of the survey results. The survey was still open so the results weren’t finalized but were consistent and in-line with what we are seeing now that the survey is closed. The results follow.
Part 1 of a 2 Part series (the second part will cover SBM Backup Implementation on SQL Server)
SBM is used to capture important information, so it is crucial that you have a good backup and restore strategy in case anything goes wrong with your database. A media failure (disk crash), user error, or an application error can each cause problems with your database where you could lose critical data; if you are not in a position to be able to restore it from your backups.
In a previous blog post, I talked about the importance of process app identity in SBM and how to change the identity of an app. In this post, we'll be discussing a more complex case that arises when sharing multiple process apps that reference each other. The essential problem is that when you change the ID of an application, if there is another application that references it, the reference may become invalid when you don't want it to. To address this, we introduced a kind of ID called a Design Number, which stays unchanged when you create a new process app from a template or create a new process app based on an existing one.
Design Parts are the logical breakdown of the Product. They allow you to break out a Product into its functional components. This breakdown is different than the physical directory structure of the Product. (Note that it’s not required to be different, but usually it is).
There are many benefits to using Design Parts.
Maria's department has a problem. Approvals are done using email, and no record is kept about who approved what and when. Approvals are sometimes lost so the approved action is not taken. People find themselves searching through their email to track down what went wrong and things feel out of control as a result. As an SBM Black Belt Ninja, Maria knows what to do, so she searches through Serena Central's Process App repository and finds a beautiful Approvals blueprint.