× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Clients with the more extensive applications do primary development on the workstation using the IBM development tools, and a WAS server loaded locally. They use a database connection set up in WAS to attach to a development partition for data access. They also maintain a WAS server on the development partition that acts as an integration test/QA site. Integration and QA are separate server instances on the partition. They deploy from the QA server to production (I think in that case they use Aldon change management). The WAS server on the partitions are kept at the same levels. The WAS server on the developers workstation my be a higher version for testing purposes.

The clients that have more modest applications have a WAS server on a development partition with two or three instances, Development, TEST/QA, or a Test instance and a QA instance. Same server for all three environments. That server might but rarely be a version higher than production, if only for a couple of weeks.

Keep in mind that you can run a WAS 7 and a WAS 8 server on the partition at the same time if you care to. In fact we are doing that right now with WAS 6 and WAS 7 preparing for the V7R1 IBM i upgrade.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 3/15/2012 10:00 AM, Jack Kingsley wrote:
Jim, could you elaborate on this on the development side. or is it you just
install it to match what your going to do on the host side as far as
versions go.

On Thu, Mar 15, 2012 at 10:44 AM, Jim Oberholtzer<midrangel@xxxxxxxxxx>wrote:

> My clients have all opted to stop at WAS-7 rather than move to WAS-8 as
> part of a V5R4 to V7 upgrade. The logic behind the decision is minimize
> change as much as possible in the OS upgrade, then move to WAS-8. One
> client has very extensive WAS applications (replaces 99.9% of BPCS with
> home code and database, one small piece left to go yet), others have
> less intensive applications. The complexity of the applications has not
> been much of a factor in the WAS version decision.
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 3/15/2012 9:36 AM, Jack Kingsley wrote:
> > Ok, I hope this is going to the correct list group. Running older WAS
> 6.0
> > on 5.4 and 6.1.1 OS. Now the problem, 7.1 os will not support the older
> > version of WAS 6.0 that we have. Should I go straight to V8 or stop at
> V7
> > or just go to 6.1 WAS(this is on the host side). Now how and what
> should I
> > do on the development side as well.
> > --
> --

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.