Abstract:
A method, apparatus and computer-usable medium aid in the writing of Java code that contains Java Naming Directory Interface (JNDI) names that refer to code artifacts in a JNDI tree structure that is stored on a server. A local copy of the JNDI tree structure is downloaded from the server to a developer workstation. JNDI names in the Java code are then validated before deployment by confirming that the JNDI names are in the local copy of the JNDI tree structure

Description:
BACKGROUND OF THE INVENTION  
       [0001]     The present invention relates in general to the field of computers and similar technologies, and in particular to software utilized in this field. Still more particularly, the present invention relates to JNDI validation.  
         [0002]     The Java Naming Directory Interface (JNDI) is a major Application Program Interface (API) for Java 2 Enterprise Edition (J2EE) development. J2EE developers use the JNDI quite often inside a number of applications. JNDI is a major life line to linking components with other components as well as linking applications with external resources that exist outside the application. JNDI is a very simple API. A developer sets up a naming context and calls a lookup( ) method. The lookup( ) method takes a literal string. This literal string makes up the name of the artifact you are looking for.  FIG. 1  depicts code  100  that shows a typical interaction with JNDI.  
         [0003]     Having literal string names as shown in  FIG. 1  allows applications not to have to know about names until the application is running. However, J2EE developers writing code have very little help when it comes to coding with JNDI. Developers often have to wait till testing to find out if there is an error inside their JNDI lookup code. Although JNDI code is commonly interspersed inside an application, developers often get the short end of the stick when it comes to JNDI validation due to problems associated with their inability to validate JNDI naming in code during initial code development.  
       SUMMARY OF THE INVENTION  
       [0004]     Recognizing the need for a solution to the above described problems, the present invention is directed to a computer-implementable method, system, and computer-usable medium designed to aid in the writing of Java code that contains Java Naming Directory Interface (JNDI) names that refer to code artifacts in a JNDI tree structure that is stored on a server. A local copy of the JNDI tree structure is downloaded from the server to a developer workstation. JNDI names in the Java code are then validated before deployment by confirming that the JNDI names are in the local copy of the JNDI tree structure.  
         [0005]     The above, as well as additional purposes, features, and advantages of the present invention will become apparent in the following detailed written description.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0006]     The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further purposes and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, where:  
         [0007]      FIG. 1  illustrates a prior art code for looking up artifacts in JNDI;  
         [0008]      FIG. 2  depicts a high-level environmental description of a JNDI naming tree being downloaded from a naming server to a developer workstation;  
         [0009]      FIG. 3  illustrates a flow-chart of exemplary steps taken to download the JNDI naming tree from the naming server to the developer workstation shown in  FIG. 2 ;  
         [0010]      FIG. 4  depicts an exemplary client computer (e.g., developer workstation) in which the present invention may implemented;  
         [0011]      FIG. 5  illustrates an exemplary server (e.g., naming server) from which software for executing the present invention may be deployed and/or implemented for the benefit of a user of the client computer shown in  FIG. 4 ;  
         [0012]      FIGS. 6   a - b  show a flow-chart of steps taken to deploy software capable of executing the steps shown and described in  FIGS. 2-3 ;  
         [0013]      FIGS. 7   a - c  show a flow-chart of steps taken to deploy in a Virtual Private Network (VPN) software that is capable of executing the steps shown and described in  FIGS. 2-3 ;  
         [0014]      FIGS. 8   a - b  show a flow-chart showing steps taken to integrate into a computer system software that is capable of executing the steps shown and described in  FIGS. 2-3 ; and  
         [0015]      FIGS. 9   a - b  show a flow-chart showing steps taken to execute the steps shown and described in  FIGS. 2-3  using an on-demand service provider.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0016]     With reference now to  FIG. 2  there is depicted a high-level environmental overview of the present invention. Briefly, a Java Naming Directory Interface (JNDI) naming tree  204  is downloaded from a naming server  206 , which is in an application server  208 , to a developer workstation  202 . As will be discussed later, the developer workstation  202  supports a local Integrated Development Environment (IDE), which includes an on-screen code editor, a compiler, a debugger, and a Graphical User Interface (GUI) builder. The IDE may be a standalone application running in developer workstation  202 , or may run in a remote location (server). The downloaded Java naming tree is then used within the IDE to confirm that JNDI names in Java code being developed in the IDE is valid (in the proper format and actually exists in the JNDI naming tree  204  that is located in naming server  206 ).  
         [0017]     Referring then to  FIG. 3 , a flow-chart showing exemplary steps taken by the present invention is shown. After initiator block  302 , a software developer specifies, within Java code being written, a JNDI address for the naming server that holds the JNDI naming tree that contains an artifact described by a literal string in a Java lookup (block  304 ). That is, whenever there is a Java lookup command in the code being written, this Java lookup command is extended to include not only the literal string name for the resource being called from the JNDI naming tree, but also where (which application server) contains that JNDI naming tree. Also in step  304 , the developer may include credentials (authorization code) as an extension of the Java lookup command. This extension is performed within a validator inside the IDE.  
         [0018]     A validator confirms two things. First, the validator (preferably an eXtensible Markup Language—XML validating parser) confirms that the format of the Java name is correct. Second, the validator confirms that the object named by the Java name is in fact found in the JNDI naming tree that is located in the naming server.  
         [0019]     As shown in block  306 , the JNDI naming tree is downloaded into the IDE&#39;s memory space. Here it is available to the IDE to confirm that JNDI names in code being developed actually exist in the JNDI naming tree (block  308 ). Thus, a pre-check is performed on the code being written before it is deployed using the IDE&#39;s validator. If the validator encounters a JNDI name with a pre-qualifier (e.g., “java:comp/env”), then it will look for a deployment descriptor (which can be specified in a setting or implied by the project type inside the IDE) and resolve the reference locally (within the developer workstation) using the downloaded copy of the JNDI naming tree.  
         [0020]     After being developed, the Java code is then deployed (block  310 ) to remote application servers, or to a local testing equivalent environment. Since the JNDI names have already been validated, there should be no errors when the newly deployed code executes and calls the JNDI in the application server, and the process ends (terminator block  312 ).  
         [0021]     Thus, the present invention provides several advantages over the prior art. First, developers can validate their code once and not have to worry about resolving names at runtime multiple times. Second, developers can verify their JNDI names against different naming servers by importing different trees. That is, different naming trees from different naming servers can be downloaded into the same IDE for use by the developer before deploying the new code. This is extremely.-helpful when moving code through various test environments involved in a typical development cycle. Furthermore, validation can be done for the existence of Enterprise Java Bean (EJB) and other Java components (factories, interfaces, objects) as well as resources such as Java DataBase Connectivity (JDBC), Java Message Service (JMS), J2EE Connector (J2C) adapters, enviromnental variables, and anyplace else where JNDI is used for lookup.  
         [0022]     A code completion feature is preferably added to an IDE (Integrated Development Environment). The IDE downloads JNDI entry information from JNDI providers that a programmer has determined he will interact with. Accordingly, when writing code, the programmer will be provided with context sensitive help. For example, say that the programmer is amidst the typing of a JNDI entry lookup in the following pseudocode: 
 
DataModelManagerEJBLocalHome localHome=(DataModelManagerEJBLocalHome) context.lookup(“java:comp/env/ejb/Da . . . ) 
 
         [0023]     As the programmer is typing the line above, the context-sensitive, code-completion feature might provide the programmer with a drop-down menu of all JNDI entries matching the pre provided text. Such a technique is used for completion of URL entries from those previously visited in an Internet browser. A programmer can choose from the list of pre-provided JNDI entries, or provide their own JNDI entry. In the example line of code above, the user might be presented with java:comp/env/ejb/DataModel.java and java:comp/env/ejb/DateCalculatejava as these are entries resident in the JNDI data available to the IDE.  
         [0024]     With reference now to  FIG. 4 , there is depicted a block diagram of an exemplary client computer  402 , in which the present invention may be utilized. Client computer  402  includes a processor unit  404  that is coupled to a system bus  406 . A video adapter  408 , which drives/supports a display  410 , is also coupled to system bus  406 . System bus  406  is coupled via a bus bridge  412  to an Input/Output (I/O) bus  414 . An I/O interface  416  is coupled to I/O bus  414 . I/ 0  interface  416  affords communication with various I/O devices, including a keyboard  418 , a mouse  420 , a Compact Disk-Read Only Memory (CD-ROM) drive  422 , a floppy disk drive  424 , and a flash drive memory  426 . The format of the ports connected to I/O interface  416  may be any known to those skilled in the art of computer architecture, including but not limited to Universal Serial Bus (USB) ports.  
         [0025]     Client computer  402  is able to communicate with a service provider server  502  via a network  428  using a network interface  430 , which is coupled to system bus  406 . Network  428  may be an external network such as the Internet, or an internal network such as an Ethernet or a Virtual Private Network (VPN). Using network  428 , client computer  402  is able to use the present invention to access service provider server  502 .  
         [0026]     A hard drive interface  432  is also coupled to system bus  406 . Hard drive interface  432  interfaces with a hard drive  434 . In a preferred embodiment, hard drive  434  populates a system memory  436 , which is also coupled to system bus  406 . Data that populates system memory  436  includes client computer  402 &#39;s operating system (OS)  438  and application programs  444 .  
         [0027]     OS  438  includes a shell  440 , for providing transparent user access to resources such as application programs  444 . Generally, shell  440  is a program that provides an interpreter and an interface between the user and the operating system. More specifically, shell  440  executes commands that are entered into a command line user interface or from a file. Thus, shell  440  (as it is called in UNIX®), also called a command processor in Windows®, is generally the highest level of the operating system software hierarchy and serves as a command interpreter. The shell provides a system prompt, interprets commands entered by keyboard, mouse, or other user input media, and sends the interpreted command(s) to the appropriate lower levels of the operating system (e.g., a kernel  442 ) for processing. Note that while shell  440  is a text-based, line-oriented user interface, the present invention will equally well support other user interface modes, such as graphical, voice, gestural, etc.  
         [0028]     As depicted, OS  438  also includes kernel  442 , which includes lower levels of functionality for OS  438 , including providing essential services required by other parts of OS  438  and application programs  444 , including memory management, process and task management, disk management, and mouse and keyboard management.  
         [0029]     Application programs  444  include a browser  446 . Browser  446  includes program modules and instructions enabling a World Wide Web (WWW) client (i.e., client computer  402 ) to send and receive network messages to the Internet using HyperText Transfer Protocol (HTTP) messaging, thus enabling communication with service provider server  502 .  
         [0030]     Application programs  444  in client computer  402 &#39;s system memory also include a JNDI Validator  448 . JNDI Validator  448  includes code for implementing the processes described in  FIGS. 2-3 . In one embodiment, client computer  402  is able to download JNDI Validator  448  from service provider server  502 .  
         [0031]     The hardware elements depicted in client computer  402  are not intended to be exhaustive, but rather are representative to highlight essential components required by the present invention. For instance, client computer  402  may include alternate memory storage devices such as magnetic cassettes, Digital Versatile Disks (DVDs), Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit and scope of the present invention.  
         [0032]     As noted above, JNDI Validator  448  can be downloaded to client computer  402  from service provider server  502 , shown in exemplary form in  FIG. 5 . Service provider server  502  includes a processor unit  504  that is coupled to a system bus  506 . A video adapter  508  is also coupled to system bus  506 . Video adapter  508  drives/supports a display  510 . System bus  506  is coupled via a bus bridge  512  to an Input/Output (I/O) bus  514 . An I/O interface  516  is coupled to I/O bus  514 . I/ 0  interface  516  affords communication with various I/O devices, including a keyboard  518 , a mouse  520 , a Compact Disk-Read Only Memory (CD-ROM) drive  522 , a floppy disk drive  524 , and a flash drive memory  526 . The format of the ports connected to I/ 0  interface  516  may be any known to those skilled in the art of computer architecture, including but not limited to Universal Serial Bus (USB) ports.  
         [0033]     Service provider server  502  is able to communicate with client computer  402  via network  428  using a network interface  530 , which is coupled to system bus  506 . Access to network  428  allows service provider server  502  to execute and/or download JNDI Validator  448  to client computer  402 .  
         [0034]     System bus  506  is also coupled to a hard drive interface  532 , which interfaces with a hard drive  534 . In a preferred embodiment, hard drive  534  populates a system memory  536 , which is also coupled to system bus  506 . Data that populates system memory  536  includes service provider server  502 &#39;s operating system  538 , which includes a shell  540  and a kernel  542 . Shell  540  is incorporated in a higher level operating system layer and utilized for providing transparent user access to resources such as application programs  544 , which include a browser  546 , and a copy of JNDI Validator  448  described above, which can be deployed to client computer  402 .  
         [0035]     The hardware elements depicted in service provider server  502  are not intended to be exhaustive, but rather are representative to highlight essential components required by the present invention. For instance, service provider server  502  may include alternate memory storage devices such as flash drives, magnetic cassettes, Digital Versatile Disks (DVDs), Bernoulli cartridges, and the like. These and other variations are intended to be within the spirit and scope of the present invention.  
         [0036]     Note further that, in a preferred embodiment of the present invention, service provider server  502  performs all of the functions associated with the present invention (including execution of JNDI Validator  448 ), thus freeing client computer  402  from using its resources.  
         [0037]     It should be understood that at least some aspects of the present invention may alternatively be implemented in a computer-useable medium that contains a program product. Programs defining functions on the present invention can be delivered to a data storage system or a computer system via a variety of signal-bearing media, which include, without limitation, non-writable storage media (e.g., CD-ROM), writable storage media (e.g., a floppy diskette, hard disk drive, read/write CD ROM, optical media), system memory including but not limited to Random Access Memory (RAM), and communication media, such as computer and telephone networks including Ethernet, the Internet, wireless networks, and like network systems. It should be understood, therefore, that such signal-bearing media when carrying or encoding computer readable instructions that direct method functions in the present invention, represent alternative embodiments of the present invention. Further, it is understood that the present invention may be implemented by a system having means in the form of hardware, software, or a combination of software and hardware as described herein or their equivalent.  
         [0000]     Software Deployment  
         [0038]     Thus, the method described herein, and in particular as shown and described in  FIGS. 2-3 , can be deployed as a process software from service provider server  502  (shown in  FIG. 5 ) to client computer  402  (shown in  FIG. 4 ).  
         [0039]     Referring then to  FIG. 6 , step  600  begins the deployment of the process software. The first thing is to determine if there are any programs that will reside on a server or servers when the process software is executed (query block  602 ). If this is the case, then the servers that will contain the executables are identified (block  604 ). The process software for the server or servers is transferred directly to the servers&#39; storage via File Transfer Protocol (FTP) or some other protocol or by copying though the use of a shared file system (block  606 ). The process software is then installed on the servers (block  608 ).  
         [0040]     Next, a determination is made on whether the process software is to be deployed by having users access the process software on a server or servers (query block  610 ). If the users are to access the process software on servers, then the server addresses that will store the process software are identified (block  612 ).  
         [0041]     A determination is made if a proxy server is to be built (query block  614 ) to store the process software. A proxy server is a server that sits between a client application, such as a Web browser, and a real server. It intercepts all requests to the real server to see if it can fulfill the requests itself. If not, it forwards the request to the real server. The two primary benefits of a proxy server are to improve performance and to filter requests. If a proxy server is required, then the proxy server is installed (block  616 ). The process software is sent to the servers either via a protocol such as FTP or it is copied directly from the source files to the server files via file sharing (block  618 ). Another embodiment would be to send a transaction to the servers that contained the process software and have the server process the transaction, then receive and copy the process software to the server&#39;s file system. Once the process software is stored at the servers, the users via their client computers, then access the process software on the servers and copy to their client computers file systems (block  620 ). Another embodiment is to have the servers automatically copy the process software to each client and then run the installation program for the process software at each client computer. The user executes the program that installs the process software on his client computer (block  622 ) then exits the process (terminator block  624 ).  
         [0042]     In query step  626 , a determination is made whether the process software is to be deployed by sending the process software to users via e-mail. The set of users where the process software will be deployed are identified together with the addresses of the user client computers (block  628 ). The process software is sent via e-mail to each of the users&#39; client computers (block  630 ). The users then receive the e-mail (block  632 ) and then detach the process software from the e-mail to a directory on their client computers (block  634 ). The user executes the program that installs the process software on his client computer (block  622 ) then exits the process (terminator block  624 ).  
         [0043]     Lastly a determination is made on whether to the process software will be sent directly to user directories on their client computers (query block  636 ). If so, the user directories are identified (block  638 ). The process software is transferred directly to the user&#39;s client computer directory (block  640 ). This can be done in several ways such as but not limited to sharing of the file system directories and then copying from the sender&#39;s file system to the recipient user&#39;s file system or alternatively using a transfer protocol such as File Transfer Protocol (FTP). The users access the directories on their client file systems in preparation for installing the process software (block  642 ). The user executes the program that installs the process software on his client computer (block  622 ) and then exits the process (terminator block  624 ).  
         [0000]     VPN Deployment  
         [0044]     The present software can be deployed to third parties as part of a service wherein a third party VPN service is offered as a secure deployment vehicle or wherein a VPN is built on-demand as required for a specific deployment.  
         [0045]     A virtual private network (VPN) is any combination of technologies that can be used to secure a connection through an otherwise unsecured or untrusted network. VPNs improve security and reduce operational costs. The VPN makes use of a public network, usually the Internet, to connect remote sites or users together. Instead of using a dedicated, real-world connection such as leased line, the VPN uses “virtual” connections routed through the Internet from the company&#39;s private network to the remote site or employee. Access to the software via a VPN can be provided as a service by specifically constructing the VPN for purposes of delivery or execution of the process software (i.e. the software resides elsewhere) wherein the lifetime of the VPN is limited to a given period of time or a given number of deployments based on an amount paid.  
         [0046]     The process software may be deployed, accessed and executed through either a remote-access or a site-to-site VPN. When using the remote-access VPNs the process software is deployed, accessed and executed via the secure, encrypted connections between a company&#39;s private network and remote users through a third-party service provider. The enterprise service provider (ESP) sets a network access server (NAS) and provides the remote users with desktop client software for their computers. The telecommuters can then dial a toll-free number or attach directly via a cable or DSL modem to reach the NAS and use their VPN client software to access the corporate network and to access, download and execute the process software.  
         [0047]     When using the site-to-site VPN, the process software is deployed, accessed and executed through the use of dedicated equipment and large-scale encryption that are used to connect a company&#39;s multiple fixed sites over a public network such as the Internet.  
         [0048]     The process software is transported over the VPN via tunneling which is the process the of placing an entire packet within another packet and sending it over a network. The protocol of the outer packet is understood by the network and both points, called runnel interfaces, where the packet enters and exits the network.  
         [0049]     The process for such VPN deployment is described in  FIG. 7 . Initiator block  702  begins the Virtual Private Network (VPN) process. A determination is made to see if a VPN for remote access is required (query block  704 ). If it is not required, then proceed to (query block  706 ). If it is required, then determine if the remote access VPN exists (query block  708 ).  
         [0050]     If a VPN does exist, then proceed to block  710 . Otherwise identify a third party provider that will provide the secure, encrypted connections between the company&#39;s private network and the company&#39;s remote users (block  712 ). The company&#39;s remote users are identified (block  714 ). The third party provider then sets up a network access server (NAS) (block  716 ) that allows the remote users to dial a toll free number or attach directly via a broadband modem to access, download and install the desktop client software for the remote-access VPN (block  718 ).  
         [0051]     After the remote access VPN has been built or if it been previously installed, the remote users can access the process software by dialing into the NAS or attaching directly via a cable or DSL modem into the NAS (block  710 ). This allows entry into the corporate network where the process software is accessed (block  720 ). The process software is transported to the remote user&#39;s desktop over the network via tunneling. That is, the process software is divided into packets and each packet including the data and protocol is placed within another packet (block  722 ). When the process software arrives at the remote user&#39;s desktop, it is removed from the packets, reconstituted and then is executed on the remote user&#39;s desktop (block  724 ).  
         [0052]     A determination is then made to see if a VPN for site to site access is required (query block  706 ). If it is not required, then proceed to exit the process (terminator block  726 ). Otherwise, determine if the site to site VPN exists (query block  728 ). If it does exist, then proceed to block  730 . Otherwise, install the dedicated equipment required to establish a site to site VPN (block  738 ). Then build the large scale encryption into the VPN (block  740 ).  
         [0053]     After the site to site VPN has been built or if it had been previously established, the users access the process software via the VPN (block  730 ). The process software is transported to the site users over the network via tunneling (block  732 ). That is, the process software is divided into packets and each packet including the data and protocol is placed within another packet (block  734 ). When the process software arrives at the remote user&#39;s desktop, it is removed from the packets, reconstituted and is executed on the site user&#39;s desktop (block  736 ). The process then ends at terminator block  726 .  
         [0000]     Software Integration  
         [0054]     The process software which consists of code for implementing the process described herein may be integrated into a client, server and network environment by providing for the process software to coexist with applications, operating systems and network operating systems software and then installing the process software on the clients and servers in the environment where the process software will function.  
         [0055]     The first step is to identify any software on the clients and servers including the network operating system where the process software will be deployed that are required by the process software or that work in conjunction with the process software. This includes the network operating system that is software that enhances a basic operating system by adding networking features.  
         [0056]     Next, the software applications and version numbers will be identified and compared to the list of software applications and version numbers that have been tested to work with the process software. Those software applications that are missing or that do not match the correct version will be upgraded with the correct version numbers. Program instructions that pass parameters from the process software to the software applications will be checked to ensure the parameter lists matches the parameter lists required by the process software. Conversely parameters passed by the software applications to the process software will be checked to ensure the parameters match the parameters required by the process software. The client and server operating systems including the network operating systems will be identified and compared to the list of operating systems, version numbers and network software that have been tested to work with the process software. Those operating systems, version numbers and network software that do not match the list of tested operating systems and version numbers will be upgraded on the clients and servers to the required level.  
         [0057]     After ensuring that the software, where the process software is to be deployed, is at the correct version level that has been tested to work with the process software, the integration is completed by installing the process software on the clients and servers.  
         [0058]     For a high-level description of this process, reference is now made to  FIG. 8 . Initiator block  802  begins the integration of the process software. The first tiling is to determine if there are any process software programs that will execute on a server or servers (block  804 ). If this is not the case, then integration proceeds to query block  806 . If this is the case, then the server addresses are identified (block  808 ). The servers are checked to see if they contain software that includes the operating system (OS), applications, and network operating systems (NOS), together with their version numbers, which have been tested with the process software (block  810 ). The servers are also checked to determine if there is any missing software that is required by the process software in block  810 .  
         [0059]     A determination is made if the version numbers match the version numbers of OS, applications and NOS that have been tested with the process software (block  812 ). If all of the versions match and there is no missing required software the integration continues in query block  806 .  
         [0060]     If one or more of the version numbers do not match, then the unmatched versions are updated on the server or servers with the correct versions (block  814 ). Additionally, if there is missing required software, then it is updated on the server or servers in the step shown in block  814 . The server integration is completed by installing the process software (block  816 ).  
         [0061]     The step shown in query block  806 , which follows either the steps shown in block  804 ,  812  or  816  determines if there are any programs of the process software that will execute on the clients. If no process software programs execute on the clients the integration proceeds to terminator block  818  and exits. If this not the case, then the client addresses are identified as shown in block  820 .  
         [0062]     The clients are checked to see if they contain software that includes the operating system (OS), applications, and network operating systems (NOS), together with their version numbers, which have been tested with the process software (block  822 ). The clients are also checked to determine if there is any missing software that is required by the process software in the step described by block  822 .  
         [0063]     A determination is made is the version numbers match the version numbers of OS, applications and NOS that have been tested with the process software (query block  824 ). If all of the versions match and there is no missing required software, then the integration proceeds to terminator block  818  and exits.  
         [0064]     If one or more of the version numbers do not match, then the unmatched versions are updated on the clients with the correct versions (block  826 ). In addition, if there is missing required software then it is updated on the clients (also block  826 ). The client integration is completed by installing the process software on the clients (block  828 ). The integration proceeds to terminator block  818  and exits.  
         [0000]     On Demand  
         [0065]     The process software is shared, simultaneously serving multiple customers in a flexible, automated fashion. It is standardized, requiring little customization and it is scalable, providing capacity on demand in a pay-as-you-go model.  
         [0066]     The process software can be stored on a shared file system accessible from one or more servers. The process software is executed via transactions that contain data and server processing requests that use CPU units on the accessed server. CPU units are units of time such as minutes, seconds, hours on the central processor of the server. Additionally the assessed server may make requests of other servers that require CPU units. CPU units are an example that represents but one measurement of use. Other measurements of use include but are not limited to network bandwidth, memory usage, storage usage, packet transfers, complete transactions etc.  
         [0067]     When multiple customers use the same process software application, their transactions are differentiated by the parameters included in the transactions that identify the unique customer and the type of service for that customer. All of the CPU units and other measurements of use that are used for the services for each customer are recorded. When the number of transactions to any one server reaches a number that begins to affect the performance of that server, other servers are accessed to increase the capacity and to share the workload. Likewise when other measurements of use such as network bandwidth, memory usage, storage usage, etc. approach a capacity so as to affect performance, additional network bandwidth, memory usage, storage etc. are added to share the workload.  
         [0068]     The measurements of use used for each service and customer are sent to a collecting server that sums the measurements of use for each customer for each service that was processed anywhere in the network of servers that provide the shared execution of the process software. The summed measurements of use units are periodically multiplied by unit costs and the resulting total process software application service costs are alternatively sent to the customer and or indicated on a web site accessed by the customer which then remits payment to the service provider.  
         [0069]     In another embodiment, the service provider requests payment directly from a customer account at a banking or financial institution.  
         [0070]     In another embodiment, if the service provider is also a customer of the customer that uses the process software application, the payment owed to the service provider is reconciled to the payment owed by the service provider to minimize the transfer of payments.  
         [0071]     With reference now to  FIG. 9 , initiator block  902  begins the On Demand process. A transaction is created than contains the unique customer identification, the requested service type and any service parameters that further, specify the type of service (block  904 ). The transaction is then sent to the main server (block  906 ). In an On Demand environment the main server can initially be the only server, then as capacity is consumed other servers are added to the On Demand environment.  
         [0072]     The server central processing unit (CPU) capacities in the On Demand environment are queried (block  908 ). The CPU requirement of the transaction is estimated, then the servers available CPU capacity in the On Demand environment are compared to the transaction CPU requirement to see if there is sufficient CPU available capacity in any server to process the transaction (query block  910 ). If there is not sufficient server CPU available capacity, then additional server CPU capacity is allocated to process the transaction (block  912 ). If there was already sufficient Available CPU capacity then the transaction is sent to a selected server (block  914 ).  
         [0073]     Before executing the transaction, a check is made of the remaining On Demand environment to determine if the environment has sufficient available capacity for processing the transaction. This environment capacity consists of such things as but not limited to network bandwidth, processor memory, storage etc. (block  916 ). If there is not sufficient available capacity, then capacity will be added to the On Demand environment (block  918 ). Next the required software to process the transaction is accessed, loaded into memory, then the transaction is executed (block  920 ).  
         [0074]     The usage measurements are recorded (block  922 ). The usage measurements consist of the portions of those functions in the On Demand environment that are used to process the transaction. The usage of such functions as, but not limited to, network bandwidth, processor memory, storage and CPU cycles are what is recorded. The usage measurements are summed, multiplied by unit costs and then recorded as a charge to the requesting customer (block  924 ).  
         [0075]     If the customer has requested that the On Demand costs be posted to a web site (query block  926 ), then they are posted (block  928 ). If the customer has requested that the On Demand costs be sent via e-mail to a customer address (query block  930 ), then these costs are sent to the customer (block  932 ). If the customer has requested that the On Demand costs be paid directly from a customer account (query block  934 ), then payment is received directly from the customer account (block  936 ). The On Demand process is then exited at terminator block  938 .  
         [0076]     While the present invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. Furthermore, as used in the specification and the appended claims, the term “computer” or “system” or “computer system” or “computing device” includes any data processing system including, but not limited to, personal computers, servers, workstations, network computers, main frame computers, routers, switches, Personal Digital Assistants (PDA&#39;s), telephones, and any other system capable of processing, transmitting, receiving, capturing and/or storing data.