Hi everybody

I´m using the Asyncrounous applet in a HATS v6.0.4 app. and it works OK on t
he test enviroment, but when I deploy the .ear file  to the WASv6.0.2 the ap
plet does not show up when the app is accesed. I have seen the  the  applica
tion.hap file in the server and the Asyncrounous update is enabled

<class name="com.ibm.hats.common.AppletSettings">

<setting name="disconnectDelay" value="300000"/>

<setting name="enable" value="true"/>

<setting name="hostname" value="10.140.29.208"/>

<setting name="ie" value="disconnect|refresh"/>

<setting name="netscape4" value="disconnect"/>

<setting name="netscape6+" value="disconnect|refresh"/>

<setting name="nonWindows" value="disconnect|refresh"/>

<setting name="other" value="disconnect|refresh"/>

<setting name="port" value="4004"/>

Have any of you experienced someting like this?,  I also noticed that one te
st app that I deployed in the WAS at the beginning sent the applet, but when
 I update this app  in order to update some changes to other features the ap
plet stop showing up even when this feature was not changed .



Regards

Ivan 

[ Post a follow-up to this message ]

In article <e6ca5s$2hs3u$1@news.boulder.ibm.com>, bacelth@hotmail.com
says...
> Hi everybody
>
> I=3Fm using the Asyncrounous applet in a HATS v6.0.4 app. and it works OK on the t
est enviroment, but when I deploy the .ear file  to the WASv6.0.2 the applet does no
t show up when the app is accesed. I have seen the  the  application.hap file in the
 se
rver and the Asyncrounous update is enabled
>
> <class name="com.ibm.hats.common.AppletSettings">
>
> <setting name="disconnectDelay" value="300000"/>
>
> <setting name="enable" value="true"/>
>
> <setting name="hostname" value="10.140.29.208"/>
>
> <setting name="ie" value="disconnect|refresh"/>
>
> <setting name="netscape4" value="disconnect"/>
>
> <setting name="netscape6+" value="disconnect|refresh"/>
>
> <setting name="nonWindows" value="disconnect|refresh"/>
>
> <setting name="other" value="disconnect|refresh"/>
>
> <setting name="port" value="4004"/>
>
> Have any of you experienced someting like this?,  I also noticed that one test app
 that I deployed in the WAS at the beginning sent the applet, but when I update this
 app  in order to update some changes to other features the applet stop showing up e
ven
when this feature was not changed .
>
>
>
>                 Regards
>
>                           Ivan
>
Are you running through a firewall that is blocking the port?

Is port 4004 being used by another application?

If you are running on iSeries with i5/OS V5R4 with the latest
maintenance, port 4004 is used by the WebFacing server.

[ Post a follow-up to this message ]

The net administrator of this company has a restriction for the users in
order to not to enable users to download or install programs to their pc. I
have asked him to change this restriction temporaly and I also change the
port that the applet was using, actually I'm using Iseries with V5R4 and the
webfacing server using the port 4004, so now the applet is using the port
1885.

The result of this changes to the net enviroment and the configuration of
the HATS app. were the following: The application now is delivering the
applet, so it works, BUT when I made this change to others apps in the same
server these other ones do not work. It seems that the Rational is not
generating the .EAR file in the correct way. I don't find other reason why
it is happening.


I have this conclution because at the very beginning I noticed that my test
app. delivers the applet but after making some changes and regenerate the
.ear file the applet does not show up again, and I did not change this
feature of the app.


Regards

Ivan




"George Baker" <gbaker@us.ibm.com> escribió en el mensaje
news:MPG.1ef636bd574c92369896d7@news.software.ibm.com...
> In article <e6ca5s$2hs3u$1@news.boulder.ibm.com>, bacelth@hotmail.com
> says... 
> Are you running through a firewall that is blocking the port?
>
> Is port 4004 being used by another application?
>
> If you are running on iSeries with i5/OS V5R4 with the latest
> maintenance, port 4004 is used by the WebFacing server.

[ Post a follow-up to this message ]

In article <e6kckm$30k1e$1@news.boulder.ibm.com>, bacelth@hotmail.com=20
says...
> The net administrator of this company has a restriction for the users in=
=20
> order to not to enable users to download or install programs to their pc.=
I=20
> have asked him to change this restriction temporaly and I also change the=
=20
> port that the applet was using, actually I'm using Iseries with V5R4 and =
the=20
> webfacing server using the port 4004, so now the applet is using the port=
=20
> 1885.
>=20
> The result of this changes to the net enviroment and the configuration of=
=20
> the HATS app. were the following: The application now is delivering the=
=20
> applet, so it works, BUT when I made this change to others apps in the sa=
me=20
> server these other ones do not work. It seems that the Rational is not=20
> generating the .EAR file in the correct way. I don't find other reason wh=
y=20
> it is happening.
>=20
>=20
> I have this conclution because at the very beginning I noticed that my te=
st=20
> app. delivers the applet but after making some changes and regenerate the=
=20[vbcol=seagreen]
> .ear file the applet does not show up again, and I did not change this=20
> feature of the app.
>=20
>=20
>                   Regards
>=20
>                         Ivan
>=20
>=20
>=20
>=20
> "George Baker" <gbaker@us.ibm.com> escribi=F3 en el mensaje=20
> news:MPG.1ef636bd574c92369896d7@news.software.ibm.com... 
ks OK=20[vbcol=seagreen] 
0.2=20[vbcol=seagreen] 
the=20[vbcol=seagreen] 
led[vbcol=seagreen] 
Probably not working because of the way you defined the port.  The=20
following is from the InfoCenter:
Port for server socket
The port that the server should use to communicate with the applet.=20
A zero (0) specifies that a random unused port above 1024 is used. You=20
can also specify a range of ports, such as 2043-4544, or a list of ports=20
delimited by commas (,), such as 3045, 1345, 9596.
Note:
If HATS is "Vertically clustered" (multiple HATS deployments on the=20
same physical machine) separate ports need to be specified for each of=20
the clones. This could be done by either editing the port on each of the=20
clones or by specifying multiple ports (using comma separated ports or a=20
range of ports) on the original HATS application. The clones will then=20
use separate ports from the specified set.

If you are using a value of 0, then that clearly is the problem. =20
Specify a list of ports, with a single entry, but be careful with=20
clusters.

[ Post a follow-up to this message ]