added support for legacy tickets
This commit is contained in:
+63
@@ -0,0 +1,63 @@
|
||||
### AS400 HTTP Server Documentation
|
||||
|
||||
To copy an Apache configuration file using an AS400 console, you'll need to use the IBM i operating system's file management tools. This involves creating a member for your HTTP server in a specific library, then using the COPY command to duplicate the configuration file.
|
||||
You can then edit the new member using the Data File Utility (DFU).
|
||||
|
||||
Here's a step-by-step guide:
|
||||
|
||||
1. Create the HTTP Server Member:
|
||||
Go to the QUSRSYS/QATMHINSTC library using the WRKMBRPDM command.
|
||||
Choose option 3 next to APACHEDFT and press F4 to prompt the COPYcommand.
|
||||
Change the TOMBR (To member) parameter to a unique name for your new HTTP server (e.g., MYAPACHE). This name cannot exceed 10 characters.
|
||||
Press Enter to accept the changes.
|
||||
|
||||
2. Edit the New Member:
|
||||
Type 18 next to the newly created member name (e.g., MYAPACHE) and press Enter.
|
||||
Page down once in the DFU.
|
||||
Modify the Instance Data value, ensuring it reflects the new configuration you want to use. For example:
|
||||
Change -apache -d /www/apachedft -f conf/httpd.conf -AutoStartN to a similar line that points to your new configuration files.
|
||||
Remember to update the paths to your configuration files (e.g., /www/MYAPACHE/conf/httpd.conf).
|
||||
|
||||
3. Create Directories and Copy Files:
|
||||
Use the 5250 command line to create the necessary directories for your new server instance:
|
||||
MKDIR '/www/MYAPACHE'
|
||||
MKDIR '/www/MYAPACHE/conf'
|
||||
MKDIR '/www/MYAPACHE/logs'
|
||||
MKDIR '/www/MYAPACHE/htdocs'
|
||||
Copy the configuration files from the source system to your new server instance using the COPY command or by using the IBM i's file management tools.
|
||||
|
||||
4. Configure the httpd.conf File (if necessary):
|
||||
Open the httpd.conf file (or apache2.conf) in a text editor.
|
||||
Make any necessary changes to the configuration, such as modifying paths, ports, or other settings as per your requirements.
|
||||
If you are setting up virtual hosts, ensure the virtual host definitions are included in the configuration file.
|
||||
Example:
|
||||
Code
|
||||
|
||||
|
||||
// Create a new member for the HTTP server
|
||||
|
||||
````
|
||||
WRKMBRPDM FILE(QUSRSYS/QATMHINSTC)
|
||||
````
|
||||
|
||||
// Select option 3 for APACHEDFT and press F4
|
||||
````
|
||||
COPY FROMBR(APACHEDFT) TOMBR(MYAPACHE)
|
||||
````
|
||||
|
||||
// Edit the new member using DFU
|
||||
|
||||
````
|
||||
WRKMBRPDM FILE(QUSRSYS/QATMHINSTC)
|
||||
````
|
||||
|
||||
// Type 18 next to MYAPACHE and press Enter
|
||||
|
||||
#### Important Notes:
|
||||
|
||||
The TOMBR parameter must be a unique name within the library.
|
||||
The new member's Instance Data must be correctly configured to point to your new Apache instance.
|
||||
Ensure you have the necessary permissions to modify the QUSRSYS/QATMHINSTClibrary.
|
||||
|
||||
You may need to restart the HTTP server after making changes to the configuration.
|
||||
This process duplicates an existing HTTP server instance. If you're configuring a new server, you may need to install Apache first, as well as configure the required directories and configuration files.
|
||||
Reference in New Issue
Block a user