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



So, what you're telling me is that there is no way to get there from
here? 

Sorry, but that's weak....

 


Mark Walter
Senior Programmer/Analyst
IBM Certified RPG Developer
Hainey Business Systems
(717) 600-0033 Ext 130
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
 

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Don Yantzi
Sent: Wednesday, December 20, 2006 9:46 AM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] SSL

SSL is currently only implemented for Windows, Linux, Unix and AIX
connections in the RSE, not for iSeries connections.  We have it as a
requirement to implement this for iSeries RSE connections (the standard
i5/OS host servers and IBM Toolbox already support this, but we would
need to implement it for the debug server as well). 

The port information you see on the Remote Systems > Communications
preference page is for a local communications daemon that runs inside of
the workbench and accepts incoming socket connections.  This is used by
the local program verifiers and remote STRRSESVR CL command.  It used to
be used by the iSeries integrated debugger but this changed in V6.0 (or
it might have been 6.0.1) so that the debugger only creates socket
connections from the PC up to the iSeries (this cuts down on the
firewall issues and eliminates the NAT problems). 

Don Yantzi
Technical Lead
WebSphere Development Studio Client for iSeries IBM Toronto Lab





"Mark Walter" <mwalter@xxxxxxxxxxx>
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
12/19/2006 02:44 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] SSL






Ok, I have 4300 open. Still no go. 


Mark Walter
Senior Programmer/Analyst
IBM Certified RPG Developer
Hainey Business Systems
(717) 600-0033 Ext 130
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
 

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Ron Power
Sent: Tuesday, December 19, 2006 1:40 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] SSL

RSE Communications daemon port number specified under Window -
Preferences
- Remote Systems - Communications

Mine says 4300

I'm just shooting at straws here with this one, but it has to be some
port...

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
709-576-8132
rpower@xxxxxxxxxx
http://www.stjohns.ca/
________________________________________________________________________
___
Success is going from failure to failure without a loss of enthusiasm. -
Sir Winston Churchill




"Mark Walter" <mwalter@xxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
2006/12/19 03:05 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] SSL






Ok,

I have all the ports open that Client Access uses. I can verify this
over the SSL connection properties in Client Access. Still can't
connect. 

Mark 


Mark Walter
Senior Programmer/Analyst
IBM Certified RPG Developer
Hainey Business Systems
(717) 600-0033 Ext 130
mwalter@xxxxxxxxxxx
http://www.hbs-inc.com
 


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.