Appeal No. 2006-2700
Application No. 10/705,456
may interface with various other types of systems, such
as specialized authentication servers, e-commerce
servers, other types of legacy systems, etc.
2. At paragraph 102, Shapiro states the following:
[0102] In one embodiment, the backend system may
implement one or more programmatically callable
functions, and step 302 may comprise obtaining
information specifying these functions. Examples of
programmatically callable functions associated with
various types of backend systems include: a specific
stored procedure, a prepared query, a BAPI, an RFC, a
psft message, an MQseries message, a CICS txn, etc. For
example, for an R/3 system, step 302 may comprise
calling an application programming interface (API)
provided by the R/3 system to obtain the information
specifying the functions. The API may also be employed
to determine input and output parameters for the
functions. As another example, for a PeopleSoft system,
step 302 may comprise executing database queries to
determine programmatically callable functions or stored
procedures. [Emphasis added.]
3. At paragraph 103, Shapiro states the following:
For example, for the R/3 and PeopleSoft examples
above, the received information may directly specify
functions available on the backend system, may specify
input and/or output parameters associated with the
functions, etc.[Emphasis added].
4. At paragraph 111, Shapiro states the following:
For example, referring again to the R/3 backend
system example discussed above, a list of
programmatically callable functions available on the
R/3 system may be returned to the client computer. The
client computer may then display this list, and the
user may select a subset of the functions that the user
wishes to be able to call from the application server.
Thus, step 306 may comprise programmatically creating
information corresponding to only the specified subset
10
Page: Previous 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Next
Last modified: September 9, 2013