The purpose of this blog is to highlight 5 key aspects IBM i (iSeries/AS400) hosting providers need to deal with when you move your applications to the cloud. Over the years we have seen a wide variety issues that can delay the process to get your hosted environment ready for “go live”.
Having a clear roadmap to prepare for hosting aligns the teams for a smooth and easy transition. And THAT is what this blog is about.
Disclaimer: IBM I is an operating system. iSeries and AS400 are IBM server names. I use them interchangeably to make it easy for web researchers to easily find this information.
We think IBM i Cloud Hosting should be easy.
And that is what we want for our client experience.
But it’s really not that easy. Here’s why:
1) The tapes that prospective clients send us can be incomplete or have “holes”,
2) Connectivity expertise and firewalls can vary widely,
3) Software keys may be missing or incomplete,
4) Testing plan definitions can vary widely,
5) “Go Live” is undetermined or incompletely planned.
Each client comes with their own set of unique circumstances. Like Forest Gump’s Mama says, “Life is like a box of chocolates. You never know what you are going to get.”
Let me elaborate.
Backup Tapes We Receive Are Not Always As Complete As We Would Like
An IBM i hosting provider needs a complete client Save21 to restore to a Logical Partition (LPAR, or for non-IBM i users, an “instance”). When properly restored, the LPAR hosts a copy of the client’s system.
We do not always get a “clean” Save21. Variations include:
1) Save21 at back-level IBM i (i.e. V5R4, V5R3) with back-level PTFs or Technology Refreshes (TR’s). In such cases, we need to bring the restored system to the most current PTF level on a supported version of IBM i.
This is extra work we do to make it easy for our clients.
2) Sometimes we receive tapes with corrupted or missing data. In such cases, we work with the client to fix the corruption or fill in the gaps.
Browser – Based Applications
3) Occasionally clients have applications that require WebSphere Application Server (WAS), Apache or Java for several of their applications. In such cases, we need to understand the release level of these programs to verify we have the appropriate release level for the IBM i release level the client wants to run. This may also require the client to provide us with the expert administrator for WAS, Apache, or Java so we can get these programs properly setup.
Connectivity Expertise And Firewalls Can Vary Widely
Most client users connect to the IBM i cloud hosting environment with Virtual Private Network (VPN) point-to-point IPsec.
This is an expertise most IBM i clients do not have. They may have some knowledge of IBM i. They rarely have VPN expertise.
The client connectivity expertise can vary widely. Some clients have in-house networking skill. Other clients rely on external connectivity consultants.
Best results occur when the host provider and the client network administrator can a schedule call when they can work together at the same time to get connectivity.
Also, despite firewall manufacturers’ claim to be Cisco-compliant, we have seen a wide variation. In a few cases, clients have had to get firewall manufacturers’ most senior technical engineers to work with our team for a successful connection.
Prospective clients need to get connectivity in place for the initial testing.
Multiple Locations And Firewalls
Some clients have multiple locations. As part of the planning process, testing multiple locations should be part of the trial testing process.
In such cases, we have found that clients that have standardized on a specific firewall get the best results to ship their firewall to us to cohost. In these cases, the client can more easily manage their firewall and the security for their network.
Suffice it to say that VPN connectivity is EASIEST with a needs discussion, proper planning and when we get all the right people together at the same time to get the right connections.
Software Keys May Be Missing Or Incomplete
Software keys are commonly required for software programs to successfully run on the IBM i operating system.
Typically, the IBM i hosting provider includes the most common IBM i programs like the operating system, compilers (aka WebSphere Development Studio, or WDS), iAccess (aka Client Access), Query400, and DB2 Query.
Clients may also want special IBM software like BRMS, Advanced Job Scheduler, and MQSeries. These unique IBM programs generally must be licensed from IBM Passport Advantage to a specific server serial number to get the required software keys.
You may also need to do your research as some IBM software that you have used is no longer supported on IBM i 7.3, like AFP (Advanced Function Printing).
Most Independent Software Vendors (ISV’s) require software keys for their software to run on a server with a serial number different than your current IBM production server. Be sure to do your research to find out what is involved to get software keys. ISV’s may also charge a transfer fee. This transfer fee may vary depending on the related IBM server software tier (i.e. P05, P10, etc.) as well as the fee the ISV charges. Be prepared as some ISV fees are pricey and may be a deal-killer.
Ultimately, it is the client’s responsibility to research what the ISV software keys requirements are as well as the related costs to run in a hosted environment.
Testing Plan Definitions Can Vary Widely
While some clients have clearly defined testing plans, many have little to no idea how to test their applications.
We assign a project leader for a new client to get ready for hosting. A key job of the project leader is to discuss and review the client needs and environment to help the client determine what needs to be tested.
For example, a new client needs to validate that their software runs properly. Initially, they need to test that their system was properly restored to the hosting environment. They need to test that they can sign on, that their software works and common routines run properly (i.e. like end of day and end of month processes). They need to test interfaces. They need to test that printers are connected and print jobs work as expected.
Like an experienced guide, the project leader prepares the new client for testing, what factors deserve attention and what are reasonable timeframes for the testing process.
“Go Live” Is Undetermined Or Incompletely Planned
With the eagerness and excitement to move to the cloud and start testing, “go live” scheduling can get over-looked.
That is why we discuss this step at the beginning of the testing process. We want to make sure our new client has a clear goal in mind. Also, because of the high demand for skilled engineers for weekend “go live” we want to be sure the technical team is ready for the weekend target the client has scheduled in advance.
Of course we are flexible for the “go live” weekend. We understand the unexpected can happen. “Go live” can be rescheduled as issues arise.
Even so, we have found it works so much better to include this as part of the initial readiness discussion than bringing it up 30-60 days later.
Conclusion
We think moving to the cloud should be easy.
Even so, there are many factors that can make the testing process harder than it needs to be.
I have highlighted just a few of the most common issues we encounter and deal with.
We have seen many more than I can write about.
With proper planning and the right team, moving to an IBM i hosted environment can be easy.
We can help with your migration to IBM i Cloud Hosting. For further assistance, email me at blosey@source-data.com or call me at 714-593-0387.
Leave a Reply