IBM HTTP-Server for AS/400 Configuration: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
No edit summary
(De-whichified)
Line 10: Line 10:
  STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)
  STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)


After some time you can then log into the admin UI with ''QSECOFR'' and take a look at the interface. Patience is a must, the server-side component is painfully slow. <ref>Ironically, IBM, who at the time was propagating browser-based interfaces as an alternative to the supposedly dusty, character based ''Green Screen'' — which feels a lot faster.</ref> However, this allows a comprehensive configuration of all server directives.
After some time you can then log into the admin UI with ''QSECOFR'' and take a look at the interface. Patience is a must, the server-side component is painfully slow. <ref>Ironically, IBM, who at the time was propagating browser-based interfaces as an alternative to the supposedly dusty, character based ''Green Screen'' — that feels a lot faster.</ref> However, this allows a comprehensive configuration of all server directives.


New directives entered via web UI are just appended to the end of an existing configuration. This is further limiting overview.
New directives entered via web UI are just appended to the end of an existing configuration. This is further limiting overview.

Revision as of 00:04, 13 March 2020

Qsicon Fixme.png This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.

Reason: Add extensive documentation about the configuration.

The configuration of the IBM HTTP-Server for AS/400 is rather poorly documented. It's possible to manually edit the configuration with WRKHTTPCFG, but

  • in the default configuration, many directives are not included (as comments),
  • the nine-line excerpt from a large text configuration isn't helpful for retaining a certain overview,
  • the editor is awkward and slow.[1]

The procedures presented here were tested with OS/400 V4R5.

There is a web-based administration interface on the AS/400, usually listening on TCP port 2001. If a connection via http fails, the server instance is not active and must be started prior to use. 

STRTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN)

After some time you can then log into the admin UI with QSECOFR and take a look at the interface. Patience is a must, the server-side component is painfully slow. [2] However, this allows a comprehensive configuration of all server directives.

New directives entered via web UI are just appended to the end of an existing configuration. This is further limiting overview.

Fortunately it is possible to load the configuration from QUSRSYS/QATMHTTPC.CONFIG via FTP/ASCII to a local workstation. From there it's easily possible to restructure it with a local editor of your choice and then upload it again. Processing with SEU is not directly possible because the configuration is in a database table file instead of a source physical file. [3]. SEU only processes members from src-pf.

Links

Footnotes

  1. ↑ This is neither SEU nor EDTF.
  2. ↑ Ironically, IBM, who at the time was propagating browser-based interfaces as an alternative to the supposedly dusty, character based Green Screen — that feels a lot faster.
  3. ↑ Error code: EDT0213.
Retrieved from "http://try-as400.pocnet.net/index.php?title=IBM_HTTP-Server_for_AS/400_Configuration&oldid=828"