Server API directive variables, Specific URL

Directive	Variable	Access path

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

NameTrans	/URL	/QSYS.LIB/MYLIB/MYGWAPI.SRVPGM:function_name IP_address_templete

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

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

Service	/URL	/QSYS.LIB/MYLIB/MYGWAPI.SRVPGM:function_name* IP_address_template

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

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

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

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

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

Server API directive variables

The variables in these directives have the following meanings:

type Used only with the Authentication directive. This variable determines if your application function is called. Valid values are:

Basic Application function is called only for basic authentication requests

*Application function is called for all requests

/URL Determines for which URLs your application function is called. URL specifications in these directives are virtual (they do not include the protocol) but a slash (/) precedes them. For example, /www.ics.raleigh.ibm.com is correct, but http://www.ics.raleigh.ibm.com is not. Valid values are:

A specific URL

Application function is called only for that URL

URL templete

Application function is called only for URLs that match the template. You can specify a template as /URL*,/*, or *.

Note: An URL template is required with the Service directive if you want path translation to occur.

/path/file

The fully qualified file name of your compiled program

:function_name

The name you gave your application function within your program

In the DataFilter directive, you must supply the names of the open, write, and close functions.

The Service directive requires an asterisk (*) after the :function_name, if you want to have access to path information.

init_string

Optional on the ServerInit directive, this can contain any

Chapter 7. Writing Server API programs 121

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.

IBM AS/400E manual Server API directive variables, Specific URL, URL templete

Models: AS/400E

Directive