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
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
It is common in small shops for people to use a server's real name to access an application, for example: http://slvdc01/tmtrack/tmtrack.dll.
This is simple and easy, but eventually you will upgrade your application and move it to a new server, then the URL for users will change, links on your intranet page have to be updated, and inevitably users will get confused and frustrated.
Instead, use a friendly alias that users can remember. Example: http://sbm.domain.com/tmtrack/tmtrack.dll.
Beyond being more resilient to changing server names, this has the added benefit of making it easier to secure with certificates, scalable, and even to provide easier access over the internet if desired. If your product (like SBM) is connected to by other integrated systems, an alias also reduces the need to update those systems as your implementation grows.
(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...
In Work Center, administrators can create and share Dashboard and other views such as Activities, Backlogs and Calendars. In SBM 10.1.5 we introduced a new feature on the Sharing tab that is available only for admins - the ability to automatically pin the shared view to the left side navigation menu. This means that each user in the sharing list will see the view automatically appear in their menu when they next log in to Work Center or even just navigate to the particular application.
Serena Service Request users have seen the following appear when they have entered words in the title field:
This message box informs users that there is a knowledge base article that has matching words in its title. Users can easily view the existing articles, and then use an article to resolve the issue without help from the help desk.
How to implement a simple application rollback scenario.
The following document describes how you can configure an SDA application process to use advanced inventory management. This then allows the application process flow to be configured to allow for a post deployment diagnostic step to be run and automate an automated rollback mechanism upon the diagnostic test not passing.
To access the document please click on the following link.
An accompanying KBTV video will be available soon.
How many times have you created a complex notification rule or escalation and wanted to test it before going live but just wish you did not have enable all of your notifications and cause heartburn for your users?
I get this question all of the time and discovered that we added this capability in version 10.1.2.
The key is the use of the out of box, "Console" channel plug in. What it does it log the email notifications in the ns.log file so you can ensure that the right notification, notifies the right people at the right time. As a bonus, it will also show up in the Work Center UI notifications.
Many of the most common questions about new releases revolve around the platform matrix. What operating systems will be supported? Will it support the latest browsers? When will the older versions of the database be dropped from the matrix? These questions are important because you need time to plan for any changes that are happening - either with your own environment or due to changing support within the product. To help with any such decisions, I'd like to share our current thoughts about what is changing in the next major release of Serena Business Manager. The next major release is tentatively planned for release by the end of CY2015.
You just added a new file to your Dimensions CM stream (or project), made a few changes and now want to check out the new feature Annotation View. Instead of seeing information about each revision, you instead get the dreaded message “COR-440000 1E Error: Item has a binary format.”
Two of the most common reasons for this to occur are:
In this blog, we'll discuss the use of the Relational Grid option of the Embedded Report widget in Composer that enables you to replace single and multi-relational field controls on custom state and transition forms. We'll also show how to filter the list of candidates by binding query controls to the grid. We recommend you use this functionality only for state forms if you are running on a version of SBM earlier than 10.1.4 because of problems when the report results were paged or filtered on transition forms. These problems were addressed in SBM 10.1.4.
When your users view or edit the value of a single or multi-relational field on a form, the values displayed and the choices offered are presented as a summary of the related record, using the Value Display Format (defined for the table) which combines static text and field values into a single string. While this can be a handy summary of the record, sometimes you'd like to see and search against other information about the related record(s).
For example, in a state form, you may wish to display something like this:
Many administrators would utilize Serena Single Sign-On with all of its security features if it would log their users on to SBM using the Windows Credentials of the user logged on to the workstation. As of SBM 10.1.2.x, Serena SSO now does "Windows Single Sign-On".
To setup Single Sign-On and Windows Authentication, setup the authentication tab of the SBM Configurator as follows. Validate user credentials against Windows domain, and user sessions are managed by Windows Authentication (SSO). SBM uses both NTLM and Negotiate.
This article discusses UI internals of SBM Work Center and provides step-by-step procedure to customize Work Center UI beyond simple header/footer changes.
Over the 17 years I have been providing consulting through our Professional Services team, I have identified a few easy tips for saving time and money as well as ensuring a successful investment.
Work with Serena to understand any prerequisites which need to be satisfied before starting the Services. This includes the following:
Next, logon to the development server via Remote Desktop.
As I talk with customers, there seems to be a misconception of Serena Single Sign-On (SSO). The result is a modern authentication system not getting adopted in favor of the status quo.
SSO is used with all of our core products, and first appeared in the TeamTrack line with SBM 2008. Despite its name, Serena Single Sign-On is not single sign on to workstation and browser. It is a mechanism for handling sessions and authentication of web services. SSO does handle browser sessions as well as web services. Think of it as Web SSO.
Serena SSO is based on working group standards for web SSO. It uses the same modern concepts for handling sessions and authentication as other authentication systems such as ADFS, Tivoli and Open SSO to name a few.
When SBM introduced custom forms, we provided a new capability to create your own designs for the forms your users see. One downside of this, as compared to quick forms, is that they did not respond to changes in the data model. For example, when you add a field to the table, the forms are not automatically updated.