|
A) yes. From our main page a customer will Logon. Websphere will process
the Logon and build a custom menu different optios may run asp or
Websphere apps
B) no the directories are not part of iis. We have this running for years
on win2003 and Websphere 6. Building a new server to replace the old and
cannot get iis connector to was 8.0 working
Sent from my iPhone
On Aug 24, 2013, at 12:59 PM, "Jack Kingsley" <iseriesflorida@xxxxxxxxx>
wrote:
two questions:
A) will this app be deployed then on the same port.
B) is the directory setup in IIS to be served via IIS.
On Fri, Aug 23, 2013 at 6:45 PM, Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx
wrote:
I am having trouble getting IIS 7.5 to connect to a WebSphere applicationrunning
server. Below is what I posted on the PCTech list but have not seen a
response. There really is no iSeries involved as this is all running on
one windows 2008 R2 server.
I have installed WebSphere 8.0 on a Windows 2008 R2 server that is
IIS 7.5. I have installed the Web Server Plug-ins for IBM WebSpherethe
Application Server on the same server. We will be running everything on
one server. (I know I should be using two server with a firewall
in-between but that will be in the future when I talk them into putting
application on to our iSeries, after we upgrade the Power 5 520 to power7
or newer systems.)list
I have several WAS application that work on port 9080. I cannot get the
plug-in to redirect me from the IIS web page to the WAS application.
I have installed fix pack 7 for both WAS server and plug-ins. I have
configured the Application Server as cciweb01. I have configured the web
server as IISwebserver. I have generated the plug-ins and propagated the
plug in and still no re-direct.
I created the sePlugins virtual directory within the web site and pointed
it to the plug in directory. E:\Program Files
(x86)\IBM\WebSphere\Plugins\config\IISwebsphere\
The only file that was in the directory is the plugin-cfg.xml file.
What am I missing?
Chris Bipes
Director of Information Services
CrossCheck, Inc.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 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 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.
As an Amazon Associate we earn from qualifying purchases.
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.