× 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.



JWalk uses a license manager server (SEALMS library) and an app server
(SEAJWK library & some IFS directories).  The two can run on different
machines; we've done that before to avoid installing the LMS on our dev
system.

It may help to know what version of JWalk & the License Manager they're
running; they should be noted in the job logs when the jobs start up.
Also would be nice to know what errors are being logged so we know why
it's not working.

As to how JWalk is configured, it's mostly through a couple of .ini &
.html files in the JWalk IFS directories.  Look for jwalk.ini and
jwalk.html or jwalkcached.html.  The parms are somewhat documented in
the file headers.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Sunday, July 09, 2006 4:23 PM
To: Midrange Mailing List
Subject: JWalk Config question

Checking the archives it looks like there might be one or two JWalk
customers on the list.

Here is the story:  I have a customer who, about 2 years ago, dropped
support for a product that, as a third party, used JWalk for their GUI.

They upgraded their box to a new i5 and the third party wanted $60,000
to "get them current" so they could get a new license for JWalk.  This
is for a P05 box that barely cost that so, of course, they looked for
alternatives.  We are slowly implementing HATS as an alternative but
"slowly" is the problem.  They really need to either get back to JWalk
running on their old box for a while longer or find a quick alternative
for the interim.

So here is the question:  I know nothing about JWalk or how it is
configured but I wonder if it is possible to configure it so that the
old 270 is the server but we point it to the new 520 for applications
and data?  I don't know enough about the JWalk architecture to know if
this is possible but it would get them out of the crack that they are
in.

If you are a JWalk user and know something about how it operates and is
configured, I could use a few pointers (and some good news...)

Thanks,

Pete Helgren

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.