Solved

websphere

Posted on 2014-07-29
5
320 Views
Last Modified: 2014-11-12
Hello,
I have a requirement to build two servers in Amazon AWS hosted environment to host IBM's Websphere amd MQ instances.
1. Can these be built on Amazon OS 64 bit instances, or do they have to be built on RHEL ?

2. Can anyone recommend approximate file system sizes or point me to a how-to article to architect the sizes of logical volumes to allocate to these instances? I am just not sure how large to make the root file system and which directories to build as logical volumes, so the server does not run out of space down the road.

Here are recommendations I have found:
For Linux, the standard WMQ product binaries placement is in /opt/ibm/mqm while in AIX the product binaries are placed in /usr/mqm. The MQ instance and configurations is placed in /var/mqm.

As shown in the CPA's AIX filesystem partition above, the /var/mqm, /var/mqm/log, /var/mqm/errors and /var/mqm/qmgrs are placed in separated partitions. This is standard practices to allocate separate filesystems for logs and errors.

The partition sizes above are for your reference as the AIX WMB server serves a lot of applications, so the log and error directories are allocated a larger size for log keeping. You may not need 10GB for log space, but do provide ample of space for trouble shooting and it can fill up quickly.

Thank you for any insight in advance!
0
Comment
Question by:Peter Kuczynski
  • 3
  • 2
5 Comments
 
LVL 35

Expert Comment

by:Gary Patterson
ID: 40227285
1. Can these be built on Amazon OS 64 bit instances,

Not sure what that means.  Websphere comes in different editions, each with different requirements.  This document describes in detail the system requirements 9including OS support) for each:

http://www-01.ibm.com/support/docview.wss?uid=swg27006921

As for number 2, disk sizing for Websphere and WMQ is completely application-dependent.  I'd need to know a lot more about the applications you will be running and processing volume to even make a guess.  Same applies to log volumes, etc.  How much log volume do you generate, and what are your retention requirements.

Typically, you'd set up a development or test server, and determine proper disk sizing by running your anticipated volumes (or a fraction of anticipated volume and extrapolate).
0
 
LVL 1

Author Comment

by:Peter Kuczynski
ID: 40227420
Thanks for your reply Gary,
I have no more information unfortunatly on this, what it really funny is the IBM guy that I also was not forthcoming on the file space requirements.
So I have no idea how this server will be used or what i/o it will generate.
It will be a DEV server so we can extrapolate from it's performance.
I am just looking for a ballpark architecture schema to get this started.
So would ballpark be, to build a 50 gb root volume and 3,  20 gb lvm's for /var/mqm/log, /var/mqm/errors and /var/mqm/qmgrs ?
Thanks again,
0
 
LVL 35

Accepted Solution

by:
Gary Patterson earned 500 total points
ID: 40227484
I don't know - I've never provisioned a server without knowing what was going to be running on it or having an idea of the developer's space requirements.  

If I was in your shoes, I'd oversize significantly, and then adjust down after I understood the real requirements.  That's an advantage of a virtualized environment - you can easily make those sort of changes.
0
 
LVL 1

Author Comment

by:Peter Kuczynski
ID: 40227936
yup, totally agree, and thank you for your help!
I made is 80 gb and 20 gb lvm for logs, will adjust from there.
0
 
LVL 1

Author Closing Comment

by:Peter Kuczynski
ID: 40227937
Excellent and timely feedback, very much appreciated.
0

Featured Post

Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Security is one of the biggest concerns when moving and migrating your data from your on-premise location to the Public Cloud.  Where is your data? Who can access it? Will it be safe from accidental deletion?  All of these questions and more are imp…
It’s 2016. Password authentication should be dead — or at least close to dying. But, unfortunately, it has not traversed Quagga stage yet. Using password authentication is like laundering hotel guest linens with a washboard — it’s Passé.
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question