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
The best just got better.
With the release of ChangeMan ZMF 8.1 a new era of software development becomes possible for the mainframe. With over 400 customer requested ideas implemented and groundbreaking innovations in cross-platform SDLC support, this release makes managing software development, from idea to deployment more streamlined, more automated and more reliable than ever.
Leading enterprises are under pressure to deliver innovation rapidly to satisfy their customers, while maintaining high quality and integrity, and reducing cost and risk. Agility and accelerated application delivery is required but companies struggle to deliver mainframe changes at the pace that the businessRead More
Today Serena is announcing ChangeMan ZMF v8, a major update to our flagship mainframe SCCM solution. Why the continued large investment by Serena in the mainframe? Read on…Read More
When figuring out why a problem is happening in SBM or any other web based product for that matter, IIS 7.0 and later offer excellent logging of problems that result in an error code coming back from the server. For example, if you are seeing an error like a 403 or 500 being displayed in your web browser, then this is a good technique to gather detailed information about where exactly the problem is happening.
When a User requests a process in SDA you can optionally ask them to select or enter inputs properties. These properties are typically passed down from the application process to the invoked component processes. In this post I will look at how to pass application process property values down to component processes and use a couple of tricks to ensure that they are requested in as user friendly way as possible.
Not everyone can be root!
One of the first questions I get from customers about installing the Serena Deployment Automation (SDA) Agent on a Linux (or Unix) machine is… can I run the agent under a dedicated account (i.e. anyone but root)? And do you provide an init file?
The answer is…YES. Yes you can. Yes we do.
In fact, Serena recommends that you create a user account dedicated to run the agent on the machine. This allows you to control who can run what and allows you stay within the IT policy and procedures.
To configure the agent to run under a dedicated account is simple.
The SBM REST widget provides an easy way to display information that is available RESTfully via 3rd party tools. The REST grid is useful for displaying data and allowing selected rows within the grid to populate other mapped fields on the form, but out-of-the-box it does not provide an easy way to drive business/process logic.
If you've used SBM much, by now you'll have encountered rules defined in Composer. In this blog, I'll walk you through how to define and use rules in your process design and explore the many common and less common ways they can be used.
Composer users have always authenticated to the Application Repository by providing username and password credentials on the repository tab of the Composer settings dialog. In SBM 10.1.5.1 we have added the smart card as a new method for authentication in Composer. This won't matter to many of our customers, but those who need it - really - need it because, for them, it is a legal requirement. As with two-way SSL, we've hidden the interface for this so that the majority of users (who don't use smart cards) won't ever see the corresponding options.
U.S. Department of Defense Common Access Card (CAC)
This is part 1 of a 3 part series.
There is no such thing as best practices. Two different teams approaching the same challenge might succeed with completely different approaches. What works well for one team may well be irrelevant for the other. What helped one team might be counter-productive for the other.
So think of the above paragraph as my disclaimer. With that out of the way, let’s proceed. ッ
Maintaining common or shared files that are used across multiple development efforts can be challenging. There are many ways to configure Dimensions CM to support this.
In this 3 part series, I will talk about the pros and cons of two different scenarios so that you can decide which approach to take. Remember that one size does not fit all; hence the reason why Dimensions CM is so adaptable and can support different processes.
At the end of each scenario, I will include how to configure Dimensions CM to support that particular scenario.
Before we get started, let’s cover some terminology and a few ground rules to avoid confusion.
This is part 2 of 3 part series. See part 1 for an overview.
In this scenario, all applications and the common code are contained in a single Dimensions CM product called Qlarius.
Each Application will have:
The Common will have:
This is part 3 of 3 part series. See part 1 for an overview.
In this scenario, all applications are in a single product (Qlarius) and the common code (Common) is contained in a separate Dimensions CM product.
Each application will have:
The Common Code will:
Composer has long supported secure communication with the Application Repository with the Use secure connection option on the Repository tab of the SBM Composer Options dialog. When you use this setting, you can be sure the server you are connecting to is the server you expect it to be, and all subsequent communications between Composer and the server are encrypted to ensure privacy.
In many scenarios, it's often desirable to allow your users to save a draft of their record before they actually submit it. While SBM doesn't have the concept of a private draft, there are some ways we can achieve the "Save as Draft" functionality. Today we're going to take a look at a few ways we can achieve this.
Have you ever felt that you spend a lot of time managing the field privileges and orderings for workflows and transitions within SBM?
There could be several reasons including:
The following recommendations will reduce the time it takes for you to maintain your SBM Process Apps. These recommendations basically all strive to make the fewest changes to your system in order to achieve the presentation needed for your users. An added benefit is that in the end your user experience will be much more consistent as well.
Have you ever had the need to query information from SBM's Application Engine database directly? Perhaps you want to report on how the system is configured, or perhaps you need to report on information in ways not available through the user interfaces.
One of the most powerful and useful features of SDA is snapshots. If you are not using snapshots, then you are not really getting the most out of SDA. In this post I will explain what a snapshot is and how to use them effectively. I will also look at some of the more mysterious snapshot features.
(Note: I attended a wonderful class facilitated by Erika recently, where she asked us to share a tip with the other attendees. A couple of my classmates wanted to see my tip, so here it is.)
My current SBM customer uses tabs. Lots and lots and lots of tabs. Progressive tabs representing workflow stages. Functional tabs representing organizational structures. Tabs for system fields, tabs for notes and attachments...
One of the things I like best about being a Solutions Architect at Serena is that I get to meet and interact with our customers face to face. Many times, these present opportunities to share best practices but also learn how our customers use our tools and what challenges they have. One common challenge has been the inability to use Rich Text capabilities or embed images to SBM Memo Fields. The use case is pretty simple.
As of SBM 10.1.4, you can enable the Submit on Behalf of Another User feature for your users. This lets service desk technicians easily submit items on behalf of business users who call the help desk.
To enable this feature, edit the Submit transition in your parent workflow, click the Options tab, and then select Allow submit on behalf of another user.
Do you have single or multi-selection fields that you need to add or maintain using SBM Composer? If you're only working with a few values, it's easy to create, update, reorder and delete them in the selection fields property editor using the command buttons, in-place editing and keyboard shortcuts (see the "Selection Field Shortcut Values" topic in Composer help).