10HTTPD_REQUEST_SERVICED

Returned by HTTP_proxy. This return code indicates that the program that called the function completed the response for this request.

11HTTPD_RESPONSE_ALREADY_COMPLETED

The function failed because the response for that request completed processing.

Server API configuration directives

Each step in the request process has a configuration directive that allows you to indicate which of your application functions you want called and run during that step. You can add these directives to your server’s configuration file by manually editing it or by using the Server API Request Processing form in the server’s Configuration and Administration forms.

Server API usage notes

Here are some notes to consider when using the Server API:

vWhen appropriate, you can indicate that you want your application function called for all URL requests or only for URL requests that match a specified mask.

vYou can also have your Authentication functions called for every request or just for those with a type of Basic.

vThe Server API directives, except for the Service and NameTrans directives, can be in any order in the configuration file. You do not need to include every Server API directive. If you do not have an application function for a particular step, just omit the corresponding directive.

vThe Service and NameTrans directives work like the Exec directive and are dependent on its occurrence and placement relative to other mapping directives within the configuration file. This means that the server processes the Service, NameTrans, Map, Pass, Exec, Redirect, and Fail directives in their sequential order within the configuration file. When it successfully maps a URL to a file, it does not read or process any other of these directives.

vYou can also have more than one configuration directive for a step. For example, you could include two NameTrans directives, each pointing to a different application function. When the server performs the name translation step, it will process your name translation functions in the order in which they appear in the configuration file.

vMultiple IP configuration (using a trailing IP address or template) is supported only for the Service and NameTrans directives.

vIf the server fails to load a specific application function or you have a ServerInit directive that does not return an OK return code, no other application functions for that compiled Server API program will be called. Any processing specific to that program which was done up to this point is ignored. Other Server API programs that you include in these directives, and their application functions, are not affected.

 

Server API directives and syntax

 

 

 

 

Directive

 

Variable

Access path

 

 

 

 

ServerInit

 

 

/QSYS.LIB/MYLIB/MYGWAPI.SRVPGM:function_name init_string

 

 

 

 

PreExit

 

 

/QSYS.LIB/MYLIB/MYGWAPI.SRVPGM:function_name

 

 

 

 

120Web Programming Guide V4R5

Page 130
Image 130
IBM AS/400E manual Server API configuration directives, Server API usage notes, Server API directives and syntax

AS/400E specifications

The IBM AS/400E, now more commonly known as IBM i, is a robust and versatile midrange server that has been designed to provide a comprehensive computing solution for businesses of all sizes. First introduced in the late 1980s, the AS/400 series has undergone multiple enhancements and rebranding, with the AS/400E being one of the notable iterations. This powerful platform is closely associated with IBM's commitment to reliability, scalability, and integrated business solutions.

One of the main features of the AS/400E is its highly integrated architecture that combines hardware and software into a cohesive system. This integration allows for seamless operations, reducing the complexity typically associated with managing disparate systems. The system is powered by IBM's proprietary OS/400 operating system, which has evolved into IBM i, featuring advanced capabilities like object-oriented programming, integrated database management, and security features that are essential for enterprise environments.

A key characteristic of the AS/400E is its robust database support, primarily through the use of DB2 for i. This integrated database management system enables efficient data handling and retrieval, facilitating real-time business analytics and reporting. Furthermore, the platform supports a variety of programming languages, including RPG, COBOL, and Java, making it flexible for developers who require diverse tools for application development.

The AS/400E is also known for its exceptional reliability and uptime, making it a preferred choice for critical business applications in industries such as finance, healthcare, and manufacturing. This reliability is backed by advanced error detection and correction mechanisms, as well as redundancy features that help prevent data loss and minimize downtime.

In terms of scalability, the AS/400E can effortlessly expand to accommodate growing business demands. Organizations can increase processing power by adding more resources without significant disruption. This scalability, combined with the system’s built-in virtualization capabilities, allows businesses to optimize resource usage and streamline operations.

Security is another defining feature of the AS/400E. The platform incorporates various layers of security measures, including user authentication, encryption, and comprehensive auditing capabilities, ensuring that sensitive business data is protected against unauthorized access.

Overall, the IBM AS/400E remains a powerful tool in the enterprise computing landscape, providing businesses with an integrated, reliable, and secure solution for their technological needs. Its enduring popularity is a testament to its capability to evolve with changing business requirements while maintaining its core attributes of high performance and stability.