iwcallback not working on remote server after upgr

we were using tst 4.5.1 and opendeploy 4.5.1 on unix 7
we have upgraded our servers to tst 5.5 product suite (tst 5.5.2 and OD
5.5.1 and all patch and sp available)

we have a few workflows that when invoked on the tst server they start a
process on a different server (OD server) and when the process is finished
on the OD server a call is made to iwcallback -s tstserverIP ...
so that the workflow would transition to the next stage of the workflow.
the iwcallback is a copy of the iwcallback from the teamsite server
/app/iw-home/bin directory
having updated the scripts and the iwcallback from the tst5.5.2 version on
the OD server I get the following error message:
/iwcallback -s 170.20.1.29 1278 0 "finish waiting"
ERROR: TeamSite's install directory (/usr/iw-home) does not exist, please
make sure TeamSite is installed correctly
TeamSite I18N initialization failure.
To run TeamSite I18N version, please make sure $iwhome/lib/locale/*.nls
exist.
Make sure the locale you are running under is supported by TeamSite.
with teamsite 4.5.1 I did not have this problem
I also use the iwsettaskcomments and iwjobvariable on the remote server
and get a similar message
question:

why am I not able to use the iwcallback funtionaliyt from a different
server (a none teamsite server) was able in tst 4.5.1? since iwcallback
has a parameter for the teamsite server

is there a way arround this problem (by copying more files from the
teamsite server to the remote server)?

Find more posts tagged with

Comments

fuzzy

I just went and copied the locale directory thinking that it might solve my problem but found that it is still not working

fuzzy

it seams like this functionality has been taken out or is a bug that they have to fix. To get arround the problem I have written a java client server program that would run the teamsite command locally on the teamsite server and would send back the output to the calling client. Therefore the calling client will initiate the call and then would get the information back. My clients are my opendeploy servers
so if on the client side I need to get a workflow variable or ask the workflow to go to the next task or change the workflow description or even get a list of editions available or anything that could be run with from the command line could be run from this client server program.
if anyone needs more information let me know.
This client server program give a lot of power to teamsite processing since from anyserver (client) any teamsite information could be retrieved.
regards

Migrateduser

fuzzy wrote: having updated the scripts and the iwcallback from the tst5.5.2 version on
the OD server I get the following error message....

How did you update the scripts? Did you use an IWOV installer, or just copy over some files. It sounds as though the scripts may not be installed correctly on the OD server.

Brinko Kobrin
Interwoven Staff Engineer

fuzzy

Hi Brinko,
the scripts that I am talking about do not come with OD but come with teamsite. So I had initally copied those scripts from the teamsite server to the OD servers.
one of the arguments to the OD scripts is -s teamsite server (look i.e at iwcallback) either the script was intended to be used bettween teamsite servers or from any server to a teamsite server. I would think that it would rather be any server to any teamsite server since not many organisations have more than one teamsite (production) server
now after the upgrade these scripts do not work as before and my guess is because of localization issues.
I got arround this problem by writting a java client server program that is initiated on the client servers (i.e OD server) and then would process the command on the requested teamsite server. Now this utility has become extreemly powerfull since I could run and get the output to the client server (i.e OD) of any teamsite functionality. i.e if I needed to know if the latest editions were deployed, or if there other active workflows.....
trust I have unleashed something extreemly powerfull for us.
to the client server program, the teamsite apis are all executed locally so all apis are available.
this is definetly a plus for the software

Migrateduser

fuzzy,

I don't understand how your Java program gets around the problem you described, but all that matters is that it works.

It sounds as though you have built something similar to Content Services, a Java API that provides remote access to TeamSite.

The commands that you are using were designed so that they can be executed on a machine other than the TeamSite server, provided that the architectures are the same (i.e., Unix to Unix, or Windows to Windows, but not between Unix and Windows.) But the intent seems to have been for the client to mount the server's file system, so installation may be problematic. The manual says that the commands look for libraries relative to the directory that contains the program.

Brinko Kobrin
Interwoven Staff Engineer

fuzzy

Hi again,
I use the commands bettween UNIX and UNIX no cross platform. Yes you are correct all that matters is that it works.
regards
Fuzzy

Farzam
ffarzanehfar@yahoo.co.uk"> ffarzanehfar@yahoo.co.uk