IT should be pretty straightforward.
Obviously you will be running a different instance for this since it's
running on a different port.
1. Make sure your other config files are listening to only specific ip
addresses and port(s), such as 80. If not, fix them.
2. Import the Certificate into DCM. Then, assign an application name to
it also in DCM.
3. Create a new instance for your SSL web service. I do this using PDM,
but you can use whatever you're comfortable with. Make sure it points to
the config file you'll create in the next step.
4. Create the config file pretty much the same as any other, except for
rest of your config items...
This assumes you're running on port 443.
Replace <ipaddress> with the IP address this will be running with.
Replace <application_name> with the application name you assign to the
certificate in DCM.
That should do it.
On Thu, Dec 13, 2012 at 10:34 AM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:
I have the following website, hosted on the System i:
Clicking Register now on that homepage takes you to:
As you can infer from the .asp, the https is hosted on a Windows server on
our internal network.
Management wants to move the https from the Windows server onto our System
I, and I'm all in on that. But it's been quite a long time (10 years?) and
many OS releases since I've done that. Can someone point me to a guide
walks me thru getting that up and going?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives