DEPLOYMENT QUESTION. AXIANT4GL (THINCLIENT)
Joe Boyle
atla38 at dsl.pipex.com
Tue Sep 20 10:00:00 CDT 2005
Hi Syed,
this is all I found,
"you will find help on deployment issues in both the Axiant4GL help and
Axiant4GL Client help options, both of which can be loaded from the
'start/programs/Axiant4GL 3.4' tab."
Regards, Joe.
-----Original Message-----
From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
[mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
Joe Boyle
Sent: 20 September 2005 13:42
To: sshahulgm at gmail.com
Cc: powerh-l at lists.sowder.com
Subject: RE: DEPLOYMENT QUESTION. AXIANT4GL (THINCLIENT)
I only ever saw one deployment take place, and this was a (supposedly)
simple test. I did’nt really follow what was going on as I was quite new to
Axiant at the time – including the general concept of thin-client
processing.
I don’t ever recall seeing any documentation on this topic, but if I find
anything in my notes I will pass it on.
I recall that the general idea was to create a deployment package, which was
a kind of self-contained reusable client-install zip file. I’m reasonably
sure that PH has to be installed separately each time and only the client
end can be customized in this way.
I suspect you are going to have to scan your Axiant docs on this one, and
get onto support to see what they might have on file, or even try the Cognos
knowledge base site – incidentally, I also found that ‘start
http://www.cognos.com’ from a dos window works perfectly.
Regards, Joe.
________________________________________
From: Syed Shahul Hameed Mustaffa [mailto:sshahulgm at gmail.com]
Sent: 20 September 2005 11:56
To: Joe Boyle
Cc: powerh-l at lists.sowder.com
Subject: Re: DEPLOYMENT QUESTION. AXIANT4GL (THINCLIENT)
Thanks Joe.
I agree with you.
PRD means my production server.
My scenario is, I have a separate machine for Development (DEV) and another
machine for production (PRD). I do not have a development license in the
PRD. That means I cannot do a remote build in the production machine. Am I
correct?
Currently I am facing a problem deploying to the production.
If you have some experience can u please summarize the steps? That will help
me a lot.
I'm trying different ways. Your tips will certainly relieve me of some
pressure.
Regards,
SYED.
On 9/20/05, Joe Boyle <atla38 at dsl.pipex.com> wrote:
I would guess that you can deploy to any client/server where the axiant
client can ping the phserver/SQLserver, or how would software houses manage
to create generic applications; and develop on any network that has the same
environment as the deployment network.
P.S. what is a PRD server ?
Regards, Joe.
________________________________________
From: Syed Shahul Hameed Mustaffa [mailto: sshahulgm at gmail.com]
Sent: 20 September 2005 07:37
To: Glenn Baxter
Cc: powerh-l at lists.sowder.com ; Joe Boyle
Subject: Re: DEPLOYMENT QUESTION. AXIANT4GL (THINCLIENT)
Dear Glenn,
I'm just sending this mail to know if you posted something and it got lost.
It happened for me.
Regards,
SYED
On 9/19/05, Syed Shahul Hameed Mustaffa < sshahulgm at gmail.com> wrote:
Thanks for your quite a long response Glenn!
My initial thin client test depolyment went well.
Will you please correct me if I'm wrong in what I've summarized below.
1. The production server should be in same network as the Axiant 4GL
development workbench. That means I cannot develop in an isolated network
and deploy the application to a PRD server in another network. (If I can
develop in a separate network and deploy the application in another network,
how do I do the deployment?)
2. Before I deploy to PRD, I have to change the DSN information (I'm using
ODBC) to point to the production.
Thanks in advance.
Best Regards,
SYED.
On 9/19/05, Glenn Baxter < Glenn at baxterit.com.au> wrote:
Hello Syed,
You will need at least 2 Build profiles to deploy your Application, and for
each a Run Profile.
Deployment {from Deploy; Application} informs you that it will override any
folder options; which can be set folder by folder to different Build
Profiles.
Once defined, you will see the form below, which invites you to select your
Build Profile – for Deployment.
Within the Build profile {Right Click Application; Open} the important field
is the Remote Build Location. This location MUST NOT be a UNC path, as the
documentation indicates. I map a drive on my development Axiant workstation
to the shared remote location as say P for Production and V for Development
etc.
These locations MUST exist.
Again on the Build Profile tab, you can set the value for the "Connection".
These WILL be different for each machine, where the HOST name may be a
machine name or an IP address.
Once you create your Build Profiles, test them from within Axiant i.e. just
build a report or such and verify the operation.
You will also be asked to choose the Run Profile.
The options here vary with the type of deployment. It is worth pushing
through and trying different options. The help is Ok also.
We did all migration and testing to a Development server.
We then built all modules to a Production server {same server, different
paths}, so had 2 Run and 2 Build profiles.
At deployment, I simply recompiled the Dictionary and build fresh QKGO files
for each user group as all programs had previously been built to the
Production server.
With Thin Client, there is no mandatory requirement to build all objects
again; depending on your prior work of course.
Always remember that Axiant caters for MANY deployment options, so at times
can be a little daunting; by way of available choices.
My best advice is to keep it simple and "get to know it". I think your
approach is sensible – do a little first!!
Sincerely
Glenn Baxter
=======================
Baxter IT Solutions Pty Ltd
456 Victoria Parade, East Melbourne
Victoria , Australia 3002
p: 03-9415-8733
m: 0412-826-503
f: 03-9415-8911
e: glenn at baxterit.com.au
=======================
________________________________________
From: Syed Shahul Hameed Mustaffa [mailto: sshahulgm at gmail.com]
Sent: Monday, 19 September 2005 4:55 PM
To: powerh-l at lists.sowder.com
Cc: Joe Boyle
Subject: DEPLOYMENT QUESTION. AXIANT4GL (THINCLIENT)
Dear Gurus,
Quick Intro: I'm migrating a PH/MPEIX application to AXIANT4GL/WINDOWS (Thin
Client).
This question does not mean my project is over.
I am preparing the production server for testing.
My plan is as follows:
First I have a small sample application (which contains only one screen) and
I need to deploy it.
This is to try deployment in its minimal form.
Then I need to deploy only a portion of the actual application first to the
production server.
Then I need to add additional screens, qtps and quizs incrementally.
Please help me with some brief tips and summary information to go ahead
with my plan.
I have gone thru the deployment documentation and have some questions.
My development and production servers are 2 different machines.
I already have installed the licenses in the production server too.
Should I have one set of Build and Run profiles for the development and
another set for the production before I start to deploy?
The connection information will differ for both servers (like windows userid
, sql server name, sqlserver id).
Kindly correct me if I am wrong in any of my points.
Thanks in advance.
Best Regards,
SYED
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
--
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l at lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
Unsubscribe: "unsubscribe <password>" in message body to
powerh-l-request at lists.sowder.com
http://lists.sowder.com/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
More information about the powerh-l
mailing list