throbber
ODBC Web Database Addon
`for Microsoft Internet Server Beta
`
`Release Notes
`
`This release contains the ODEC Web Database addon for the beta software of the
`Internet Server for Windows NT that you received near the end of AugusL It
`contains the Open Data Base Connectivity ODBC components to enable access
`Microsoft SQL Server database from the Web Server service
`the Microsoft Internet
`Server Although this release contains only the ODBC driver for Microsoft SQL Servers
`you can use other ODBC drivers in similar manner by installing the driver and
`for use by the Web Sthcr
`configuring it
`
`to
`
`Again weed like
`
`thank you for beta testing the Microsoft Internet Server for the
`Windows NT Server version 331 operating system Before installing this ODBC add
`
`release please read these release notes completely They contain
`on to the beta
`important information for ensuring proper installation and usage of Microsoft Internet
`Server with this added functionality This document should be used in addition to and
`in place of the documentation and software you received with the Microsoft
`not
`Internet
`Server for Windows NT Sewen
`For setup instructions please refer to pages I723
`
`Overview of database access from the nternet Server
`With the Web Server and 0DB
`you can
`Create Web pages with information contained in
`database
`Insert update and delete information in the database based on user input from
`Web page
`Perform other SQL commands
`database access
`
`by the Internet Seer as shown in Figure
`
`is
`
`Figure
`
`Conceptual view of database access from the World Wide Web
`
`MSSUB EPIC
`000004
`
`Petitioner IBM – Ex. 1038, p. 1
`
`

`
`Microsoft ntemet Server Beta
`Web Database Meose Aetease Noth
`
`9/2711995
`
`or browsers front
`Web browsers such as the one included in the Internet Server beta
`other companies such as Netscape submit requests to the Internet server by using
`HyperText Transport Protocol HTIP The Internet Server
`document
`responds with
`fonnatted in HyperText Maikup Language HTIvti Access to databases La accomplished
`component of the Internet Server called internet Database Connectar one of
`through
`family of Internet Server Extensions The Database Connector is Dyna icLirik Library
`DLL file Httpcdhcdil
`that uses ODBC to access databases
`
`Figure ShOWS the components
`
`for accessing databases from the Internet Server
`
`Dtabese
`
`Connector
`
`ODBCdi
`
`Daebases
`
`MD flts
`
`SQLScrvei
`
`datsrr
`
`Other DEMS
`data
`
`Figure
`
`Database access-components
`
`on the Internet Server
`
`Httpodbcdll uses two types of tiles to control how the database is accessed and how the
`output Web page is constructed These tiles are Web Dalabase Gateway WDG files and
`HTML extension Ifl
`
`files
`
`to the desired ODBC data
`The WDG files contain the necessary information to connect
`source and execute the SQL statement WDG file also contains the name and location
`of the HTX file
`
`The HTX file is the template for the actual HTML document
`that will be returned to the
`Web browser after the database information has been merged into itby Hctpodbc.dlL
`
`The following example shows how Web browser requests information from the
`Database Connector and how that information is returned
`
`An example database query
`simple Web page called Samplehtm The sample Web page
`This example starts with
`query being executed with the results
`will contain one hyperlink that will result in
`
`MS-SUB EPIC
`000005
`
`Petitioner IBM – Ex. 1038, p. 2
`
`

`
`Mreaoft
`Inlemal Ser4et Beta
`Web Oatebase Areese Retease Ntaas
`
`912711095
`
`returned as another Wcb page Samplehtm is located in the root directory of the
`enclosed compact disc installation instructions are at the end of this Uocument Figure
`Internet Explorer assuming that the
`is displayed by Microsoft
`shows Sarnple.hun as it
`Internet Server
`
`WUcrosoft
`
`Internet Server
`
`Database Access Sample
`
`ewe
`
`Figure
`
`Samp1ehtr as seen in Internet Explorer
`
`When the hyperlink Click here to run query is clicked another Uniform Resource Locator
`URL is sent to the server The URL preccdes th hyperlink text it
`is formatted as
`bidden text
`
`HREFhttp1 /webserver/seripts/httpodbc
`dgC1iek here to run uery/A
`
`dll/scripts/saInp1e
`
`is referenced in the URL as is the
`As you can see the Database Connector Httpodbcd1l
`WDO tile for Htcpodbcdl1 to use SampIewdg Both are located in
`subdirectory called
`subthrectoxy of the Web root directoy you selected when you
`\Sciipts which is
`installed the internet Server beta The default root directory for Web services is
`c\wwwroot Note Although it appears to be one long path name after hup/webserver
`there are two distinct path names in the URL
`specifies the path of the program for the Internet Server to
`/scrpsfhttpodbcdU
`
`in fact
`
`run
`/scripts/sarnp1ewdg specifies the path of the file to be passed to Httpodbcdll
`
`On the Internet Server the entire process of using the Database Connector
`six steps as shown in Figure
`
`is perfonned in
`
`MSSUB EPIC
`000006
`
`Petitioner IBM – Ex. 1038, p. 3
`
`

`
`Mnrosott
`
`fntemet Server Beta
`
`Web Database cea Retease Notes
`
`9f2711 995
`
`Figure
`
`The six steps
`
`in the Internet Server
`
`The URL is received by the Internet Server
`Step
`The URL sent by the Web browser actuaily contains the name of the Database Connector
`and the name of the WDG file to be used Samp1ewdg is shown here but
`HttpodbcdI1
`is shown in Figure
`
`any name
`
`Figure
`
`Step
`
`the URL is received by the Internet Server
`
`MSSUB EPIC
`000007
`
`Petitioner IBM – Ex. 1038, p. 4
`
`

`
`Micosott
`
`treme Srve Be
`
`The Internet Server
`Step
`information in the URL
`Httpadbc 411 obtains the name of the WDG file and other ithms from the URL passed to
`the Internet Server shown in Figured
`
`loads Httpodbcdl1 and provides it with the remainLug
`
`and
`
`hit
`
`etterver calls Httpodbc.dII
`
`reads the WOG file
`Step
`Httpodbc4ll
`The WDG FIle contains scvral envies in the format
`field value
`In the Sampie.wdg file the ODBC data source is specified by
`Datasource Web QL
`And the HTX file is specified by
`Template saniplehtx
`Here is the file Sample.wdg referenced in the URL above
`Datsource Web SQL
`Username 88
`Template
`xple.htic
`SQLStatement
`SELECT aulnaxne ytdsales
`from pubs.dbo.titleview
`where ytdsa1es5OOO
`In the Sample.wdg file also provided in the root directory of your compact disc the data
`source name is Web SQL The ODBC installation notes in the next section step through
`data source called Web SQL that refers to SQL Server
`creating
`The other items contained in Sample.wdg include
`valid login to SQL Server
`The Username which must be
`Template which specifies the file to use to merge the results
`the SQL statement to execute
`SQLStatement which contains
`Sec the Features of the Database Connector section of this document for definitions for
`all the fields that can be specified in WDG files
`
`the author last names and year4odate
`in Sa plewd returns all
`The SQLStatement
`sales amounts from the pubs sample database in SQL Server for authors whose books
`have year$o-date sales of more than 5000 copies
`
`MSSUB EPIC
`000008
`
`Petitioner IBM – Ex. 1038, p. 5
`
`

`
`Mbosort ntomt SerBeta
`Dsecs5 Reae Notes
`
`9/271995
`
`Figure
`
`shows the process through Step
`
`SAMPLEWDG
`
`F1
`
`tOub.3
`
`todbc 411 reads Samp1ewdg
`
`Bttpodbcd1l connects to the ODBC data source and executes the SQL
`Step
`statement contained within the WflG file
`The connection is made to the ODBC data source by Httpodbc4ll which in this example
`loads the ODBC driver for SQL Server and connects to the server specified in the
`definition of the data source Once the comiection is made the SQLstatement
`in the
`WDG file is sent to the SQL Server ODBC driver which in turn sends it to SQL Server
`The interaction with ODBC is shown in Figure
`
`MS-SUB EPIC
`000009
`
`Petitioner IBM – Ex. 1038, p. 6
`
`

`
`Microsoft lntwnel Seiver Beta
`Web Database Access Release Notes
`
`9/27/1995
`
`SMPLEWOC
`
`ta Web SQL
`
`SQL Server
`data
`
`dntècting to the ODBC data source and executing the
`
`query
`
`Step
`
`Httpodbc.dll
`
`fetches
`
`the data frOm the database and merges it
`
`into the RTX
`
`tile
`
`reads the HTX file specified in
`After the SQL statement has been executed Httpodbc.dll
`Sample.wdg SarnpIehtx and replaces every placeholder with the actual data returned by
`the query
`The Sample.htx file is an HTML document tjian contains placebotders for data returned
`from the database the placeholders are shown in bold for clarity
`HTMLEAD
`T/ tAtECERATOW
`fH5AD
`BODY
`eHi
`Microsort 1ntenet Server
`Dabaae cceas Sasp1 /H2
`
`7XTLEHTe docuaent
`
`for
`
`the WotId W4O Wb FTtTL
`TInrnat Aaaitat for WOsd 2.0 BctA
`
`here are the reau1ta
`
`YTC $elea/
`5wthor
`gLdetefl
`
`/PRF
`
`The web pege you see here was created by eer9in9 the restilts of
`apieht
`sapiaw4 with the teeptate
`file
`
`the query specified
`
`MSSUB EPIC
`000010
`
`Petitioner IBM – Ex. 1038, p. 7
`
`

`
`Mlcrsft ntsmet Swve Bets
`Web Datab5sG Access RelSeeO Holes
`
`9127/995
`
`The serge was done by the oaabese Cennactor Rttpsdbcd11
`Internet Server
`to this Web browser by the Microsoft
`
`aed the reesite were returted
`
`The %begindetait% and %enddetail% sections delimit where rows returned from
`in the document Columns returned from the query are
`the database will appear
`
`surrounded by %%such as %au_lnaine% and %ytdsales%in the preceding
`
`example
`
`shows the process upto the data retrieval
`Figure
`the Samplehtx file
`
`from the data source and merge with
`
`SM1PLWDG
`
`ConneeL Ww SQL
`
`ExciELECT.
`
`SQL Server
`thie
`
`Figure
`
`Steps 1-5 data retrieval and merge with
`
`Httpodbc.dfl sends the merged document back to the Internet Servers whkh
`Step
`returns it
`to the client
`After all the data has been merged into the placeholders in Sample.htx the complete
`is sent back to the client Figure 10 shows the process through step
`document
`returning
`the merged document back to the client Web browser Step
`has been omitted from the
`diagram for clarity
`
`MSSUB EPIC
`000011
`
`Petitioner IBM – Ex. 1038, p. 8
`
`

`
`Mroaft ntcmet erver8%a
`PCCeS3 Reteae Noe
`Web Database
`
`912711995
`
`SAMPLEWG
`
`1SQL1
`
`SQL Scr
`
`data
`
`To Web
`bmwect
`
`Figure lO Returning HTML document
`
`to the client Web browser
`
`And the resulting Web page is displayed in the Microsoft NT Internet Explorer as shown
`inPigure 11
`
`MSSUB EPIC
`000012
`
`Petitioner IBM – Ex. 1038, p. 9
`
`

`
`Internet Server 8oa
`Mcrofl
`Web Oetabase Acass Release Notes
`
`____
`
`10
`
`Cr27/1995
`
`Database Access Samp$e
`
`Mere are the results
`
`itho
`cei
`
`TD S1es
`
`19Z2
`
`DeFrertee
`
`22245
`
`22245
`Ringer
`Cnon 780
`
`oehetHeUa
`
`1O95
`
`The web page you see here was created by merging the results of the
`SAMPLE WOO with the template TUe SAMPLEHTX
`query specifIed
`The merge was done by the Database Connector MTTPODCDLL and the
`results were returned to this Web browser by the MIcrosoft ntemet Seiver
`
`Output Web page containing the results of the query
`
`Features of the Database Connector
`The Database Connector has several
`features to provide additional
`creating Web pages that contain data from database
`
`functionality for
`
`31
`WOG files
`As seen the examples above WDG files contain the informatIon used to access the
`database The following section describes the features of WOO files
`
`31i Parameters
`The exampk in the preceding section shows only the simplest kind of query
`query
`which was defined completely in the WDO file on the Internet server Although this type
`of query is useful even more powerful Web pages can be constructed through the use of
`
`MSSUB EPIC
`000013
`
`Petitioner IBM – Ex. 1038, p. 10
`
`

`
`Mrosoft
`
`tme Swvr Boa
`VDba AcceSS Rea Nôte
`
`11
`W271996
`
`paromeers Parameters the names and values of HTML form controls such as ThPUT
`and names specified direcdy in URLs These are sent by Web browsers and can be
`used in SQL statemeuls on the server
`
`For exarnpk in the last section the query in Sainplewdg returned only the authors whose
`parameter we could build Web page that
`yearrodate sales exceeded 5000By using
`asks the user to decide what number to use instead of 5000
`
`The Web page needs to prompt th user for the year4odate sales figure an then name
`the associated variable to .raler Sample2htm included on the compact disc shows
`ield used toobraln
`
`Microsoft
`
`Internet Server
`
`Database Access Sampe2
`
`Enter YTO saes amount
`
`Figure 12 Saaple2htm
`
`The HTML syntax for the input field and button in Samplt2htm is
`FOR4 NRODPOS
`thr YTD s1es aomt NTJT AEaa VLtJZ5QOO
`rnir IYPE- sUNT1
`/VoH
`
`JALTh- Run
`
`In the WDG flu you use the parameter in pisce
`SELEcr aL1nwRe
`pub dbtiUeviw
`vbere ytsa
`it corresponds to the EPUT NAr
`Here the parameter name must be sales so that
`on the Web page Parameters must be enclosed with percent characters
`sales
`an SQL
`distinguish them from normal
`
`the number 5000
`
`identifier
`
`to
`
`MS-SUB EPIC
`000014
`
`Petitioner IBM – Ex. 1038, p. 11
`
`

`
`Mrostl etemeT Swver Beta
`Web Database cee Retaase Notes
`
`12
`W21/995
`
`You can build powerful collections of Web pages by using the output of one query to
`provide links to other queries For example to show the titles for an inthvidual author
`instead of returning the author name as plain text you can embed it with
`link1 and then
`use the link to do another query
`
`The final example included on the compact disc shows how to do this type of linkage
`Sample3.htin is used to run the query in Sample3.wdg which uses Sample3.htx for the
`template Sainple3 .htx will return author last names as links which when clicked
`output
`.on will display the titles for each author using Sample3a.wdg and Sample3a.htx
`
`.3.1.2 Fields in WDG tiles
`The following table lists the fields that can be specified in WDG ifie Field names in
`bold are required
`
`Datasource
`
`Usernarne
`
`Password
`
`MaxFieldSize
`
`MaxRecords
`
`Template
`
`RequiredParameters
`
`DefaultParameters
`
`Expires
`
`SQLStaternent
`
`The name that corresponds to the data source name you created
`earlier by using the ODBC Administrator
`valid user name with access to the SQL Server This field is
`the SQL Server is not running integrated security
`required if
`Note If the SQL Servà is running integrated security the
`Username field will be ignored even if it
`is supplied
`The password that corresponds to the user name If the password is
`null this field can be left out Note If the SQL server is running
`integrated security the password will be ignored
`The maximum buffer space allocated by Httpodbc.dll
`Any characters beyond thIs will be truncated
`The maximum number of records that httpodbc.dul will return from
`
`per record
`
`The name of the .MTX file that will be used to format the data
`when the data from tbique is returned
`The parameter names if any that httpodbc.dU will ensure are
`passed from the client or will return an error
`The parameter values if any that will be used in the WDG file if
`parameter is not specified kythe client
`cached output
`The number of seconds to want before refreshing
`caches the Web page sent to the
`page By defaultHttpodbc.dll
`request is identical the cached page will be
`client
`subsequent
`If
`returned without ever accessing the database The Expires field is
`useful when you want to force
`requery of the database after
`certain ueriod of time
`The SQL statement to execute The SQL Statement can contain
`parameter values from the cicnt which must be enclosed with
`percent characters The SQLstatement can occupy multiple lines in
`the WIXI
`field each subsequent
`file Following the SQLStatement
`will be considered part of the
`
`line beginning with
`
`plus sign
`
`field
`
`MSSUB EPIC
`000015
`
`Petitioner IBM – Ex. 1038, p. 12
`
`

`
`Mcroso InimeL SVP Beta
`Web
`
`32
`HTX Fifes
`number of keyords that control how the output HTML document
`HTX files contain
`constructed These keywords are explained below
`
`is
`
`32.1 %begindetai% %enddetail%
`section of the HTX
`The %begindetail% %enddetail% keywords surround
`from the database will be merged Within the seedon
`in which the data Qutput
`document
`the column names delimited with
`are used to mark the position of the
`and
`returned data from the query For examples
`
`begindetai1%
`
`%enddeteil%
`
`.%ytdsa1as%
`
`list
`
`the columns aujnaine and ytd_sales Any column can be referred to in this way
`will
`Column names can also be refened to elsewhere in the JflX Note If
`there are no records
`returned from the query the %bvgindetail% section Will be skipped
`
`32.2 %f%..%else%..%endif%
`HTX files can contain conditional
`logic with an ifthenelse statement
`Web page is constructed For example one common usage is to insert
`row within %begindetail%
`display the column names from the query on the first
`section but if there are no records returned by the query display the text No records
`found By using the %lf%statement and builtin variable called CurrentRecord
`you can tailor the output so that the headers are not printed when no records are returned
`as they are in the example shown in the last section Here is an example showing the use
`of the %if%statement
`
`to control how the
`
`condition to
`
`%begindetai1%
`air CirrentPecord EQ
`Bxuthor
`YTO Sales/B
`z%endif%
`HREF
`/scpt/httpodbcd11/scripts/sanp1e3awdg1name%au_1name%%
`u_1nezne%/A %ytda1e%
`enOdeti 1%
`air CurrentRecord EQ
`No eeords e1ectecU
`%endif%
`
`The general syntax is
`%if condition
`HTML text
`
`HTML text
`%endif%
`Where coldifton is of the form
`
`MSSUB EPIC
`000016
`
`Petitioner IBM – Ex. 1038, p. 13
`
`

`
`Motttnemat Savor8ta
`Web Database Accs Roloase Notes
`
`8/2711995
`
`value operator value2
`and operator can be one of the followinR
`EQ
`LT
`OT
`CONTAII4S
`
`if value equals value2
`
`if value is less than value2
`
`if valuel
`than value2
`is greater
`part of value contains the stdnylue2
`
`The operands valuel and value2 can be column names one of the built-in variabics
`CurrentRecord or MaxRecords see below an HTFP variable name see below or
`vonstant When used in an %if%statement values ye not delimited with
`and
`For example to do special processing on author name Greerf use the condition
`
`%begindetail%
`%if au3nase EQ Green%
`this guy is areen
`%endi
`%enCdeti 1%
`
`The %if%statement can also be used to do special processing based on information
`from HTP variables For example to format
`page differently based on the typo of
`client Web browser you could include the following in the HTX file
`
`%jf WrP_usERAGft
`client
`is Netscape
`
`cQntsjfls Nozi1la%
`
`is %HTTPUEERAGENT%
`client
`%endif%
`
`323 CurrentRecord MaxRecords
`The CdlTentRecord built-in variabe contains
`the number of times the %begindetail%
`section has been processed The first
`time through the %begiudetail% section the
`value is zero Subsequently the value of CurrentRecord changes every time another
`record is fetched from the database
`
`The MaxRecords bui1tin variable cantains the value of the MaxRecords field in the
`WDG fll
`
`324 Parameters from WDG tiles
`Parameters from WDG files may be accessed in the HTX file by prefixing the name of
`the parameter with wdg and
`period In Samplc3Ji shown eariler you could show
`the value of the parameter %sales% by including the line
`
`The value of
`
`the sales parameter
`
`is- %wdgsales%
`
`325 HTTP variables
`Several variables can be used hi HTX files which give
`lot of information about
`environment and Web client connected to the server The table below gives
`listing of the information available
`
`thc
`
`partial
`
`MS-SUB EPIC
`000017
`
`Petitioner IBM – Ex. 1038, p. 14
`
`

`
`Moscft ntem1 Sewr eia
`Web Otbase Acs Release Notes
`
`9127119S5
`
`flTTP variable
`ALLHITP
`
`AUTH_PASS
`
`AUTH_TYPE
`
`CoNTENTLENGTH
`
`CDNThNTJYPE
`
`GATE WAY_fl4TERFACE
`
`I-ITFP_ACCEPT
`
`PATH_TRANSLATED
`
`Meaning
`All HTFP headers that were not already parsed into one of
`the form
`the above
`These variables are of
`variables
`field name for cxemple
`H1rP4lcader
`qQ3OO auaio/xai-fff
`WITPACCEPT
`image/jpeg image/gf
`text/pIain
`audiofbasic
`text/tru3
`HrP_USER_AGENT Mirooft
`E1orer/O.1 Win32
`HPPP_REF2RER
`htm
`http /fwebser er/scripts/max1e3
`RTTPCONTTYPE
`app1ieation/x-xwtQrm
`ur1encoed
`
`Interiet
`
`HTTP EXTENSION Security/Pigest
`
`This
`
`will
`
`retrieve
`
`the
`
`password
`
`corresponding
`
`to
`
`authenticated
`
`The type of authorization in se If the usemame has been
`contain Basic
`this will
`by the
`server
`it will not be scnt
`The number of bytes which the script can expect to receive
`from the client
`The content
`
`type of the information supplied in the body of
`
`the CGI Common Gateway Interface
`The revision of
`specification to which this server comp1ies The current
`version is CGIJL1
`Special case HTFP header Values of the Accept
`Eg if
`the foLlowing
`are concatenated separated by
`lines are part of the HTFP header
`
`fields
`
`accept
`
`accept
`
`qaj
`
`textfhtrnl
`
`accept
`
`imagejpeg
`
`then the HTIP_ACCEFF variable will have
`
`value of
`
`qal text/html
`
`image5pcg
`
`Additional path information as given by the client This
`compdses the trailing part of the URL after the script name
`
`This is the value of PATHIFO but with any virtual path
`
`ification
`
`The information which follows the
`
`in the URL which
`
`MS-SUB EPIC
`000018
`
`Petitioner IBM – Ex. 1038, p. 15
`
`

`
`Microsoft 1nieet Sosvor Beic
`Wb Databa Atcess Reasa Notos
`
`16
`
`REMOTE ADDR
`REMOTE_HOST
`REMOTE_USER
`
`SCRIPT_NA
`SERVER_NAME
`
`The
`
`address of the client
`
`The hostname of the clint
`
`authenticatcd
`
`This contains
`
`supplied by the client and
`the username
`by the server REQUEST_lvTHOD String
`jeuestnethod
`The name of the script program being executed
`The servers hoatname or IP address as it should appear
`
`SERVER PORT
`SERVER_PROTOCOL
`
`The TCP/U port on which the request was received
`The name and version of the information retrieval protocol
`
`SERVER_s0FrWARE
`
`The name and version of the Web Server under which the
`CG1proam or Internet Server Extension is running
`
`The complete list of HiT variables will be provided with the final documentation for
`the Internet Server
`
`MS-SUB EPIC
`000019
`
`Petitioner IBM – Ex. 1038, p. 16
`
`

`
`Mlcrceoft nteme Server Eeta
`Web
`aaae Access Release Notes
`
`17
`912 Th995
`
`nstaHing ODBC and the SQL Server ODBC driver
`
`Run Setup.exe from the directoty on the enclosed conlp4ct disc named for your
`platform For example for Intal platforms OU can run Setup from the Program Manager
`by choosing File Run and entering the information shown in Figure 13 assuming your
`CDROM drive is Drive
`
`Qmeland Line
`
`aun Mlnimxed
`lice ui Sepeiatc pmeiy Spec
`
`_________
`
`Figure 13 Running ODBC Setup
`
`The ODBC Setup dialog box appea as shown in Figure 14
`
`Ii
`
`Figure 14 The ODBC Setup
`
`the ODBC driver list
`Click the Continue button The next dialog box will present
`In this
`case only the SQL Server driver is available Click the SQL Seerent13 in the list box as
`shown in Figure 15
`
`MSSUB EPIC
`000020
`
`Petitioner IBM – Ex. 1038, p. 17
`
`

`
`Microsoft ntrnm Saver Bti
`Wsb Databav Access Release Notes
`
`18
`
`9tZTfl995
`
`Figure 15 SeIect
`
`driver
`
`________
`
`Petitioner IBM – Ex. 1038, p. 18
`
`

`
`Mcoot1 ntemet $er 8e
`Data baze cea Aaoase Notes
`
`19
`
`9f27fl$9
`
`Figure 18 Add bátá Sbrce
`
`list of ODBC drivers than that shown in Figure 18 If you have
`You may have
`never installed ODBC components on your computer before only the SQL Server driver
`will appear in the list box
`
`different
`
`Select SQL Server from the list box and click OK The ODBC SQL Server Setup dialog
`box will appear as shown in Figure 19
`
`MSSUD EPIC
`000022
`
`Petitioner IBM – Ex. 1038, p. 19
`
`

`
`
`20
`Microsoft Internet Server Beta
`20
`
`Web Database Access Release Notes 9/2711995 7
`0t7F195
`
`‘'
`(3080 SQL Se'nre_r'$ctu|1
`
`"3‘-it‘.-‘-en."
`
`.-u-‘-1-::“'‘
`
`_[_I PAFNKR1
`
`'lTlSTS .
`- mrsrsv
`
`Figure 19: SQL Server Setup dialog box
`
`Entcruthe name of the data source. The data source name is a logical name used by ODBC
`to refer to the SQL Server driver and the actual server name on which SQL Server is
`running. You can also use the server name "(local)" if SQL Server is running on this
`computer. The data source name is used in WDG files to tell the ‘Web Server where to
`access the data.
`
`In Figure 19, the data source name “Web SQL" was entered and the SQL Server
`“N’I"I‘S'I'SR " is selected. "Web SQL" was used in a earlier examples, so you should use
`that name for now. Later, you can change it if you like. The server name, network
`address. and network library are specific to your installation. If you do not know what to
`enter in these controls accept the defaults. To find out the details, click the Help button
`and find the section that describes your network.
`
`After the data source name and server name have been entered, click OK. The System
`Data Sources dialog box will be displayed again, but now will have the name of the data
`source displayed as shown in Figure 20:
`
`,.
`
`System ala Source;
`
`
`
`‘fig,
`
`MS-SUB EPIC
`
`'
`
`000023
`
`Petitioner IBM — Ex. 1038, p. 20
`
`Petitioner IBM – Ex. 1038, p. 20
`
`

`
`
`
`Microsoft Ihiemel Sewer Beta
`Web Database Access Release Notes
`
`'
`
`21
`9/2731995
`
`Click Close. The Data Sources dialog box is displayed again as shown in Figure 21:
`
`
`
`Figure 21: Data sources dialog box.
`
`Click Close. The final completion dialog box of ODBC Setup is displayed. Click OK. and
`the ODBC Setup is complete.
`
`.
`
`V
`
`l
`
`_
`
`MS-SUB EPIC
`
`-
`
`.
`
`000024
`
`'""-""—' "" "'_ ”""‘" " "'"
`
`" """'
`
`“ """ “""""""—“"
`
`_
`
`.
`
`.. ..
`
`.
`
`.__,
`
`Petitioner IBM – Ex. 1038, p. 21
`
`

`
`Mcrnsott nteme Sever Dea
`Web Oatase Access Roease Noise
`
`97II995
`
`Installing the sampe files used in this document
`
`The sample files specified in section 3J are included on the compact disc in the root
`directo In order to use the samples you must copy them to the correct directory on your
`Inteniet Server computer You must also create
`new subdirecto and copy the Database
`to that directory You can use the File Manager or the command
`Connector Httpodbc4ll
`prompt on the computer running the Internet Server Finally in order to use the samples
`the following must be true
`
`You must have access to Microsoft SQL Server and know the name of the computer
`is running FusThermore for the samples to run as is the sa account
`on which it
`from your computer and the an account must have no password
`must be accessible
`installation for Microsoft SQL Server If you cannot or do not
`This is the default
`wish to use the sa account
`for these samples you can change the Username field
`and add Password fleld if necessary in Samplewdg Sample2wdg and
`valid user account
`Sample3.wdg to
`
`You must run the ODBC setup procedure as described in the previous section of this
`called Web SQL
`document Specifically you must create an ODBC Datasourco
`If you installed ODBC but
`associate it with an NT server running SQL Server
`just need to create the ODBC Datasource you can do so by using the ODBC control
`panel device in the NT control panel
`Just double click on the ODBC icon and
`youll be able to follow the steps to create the Web SQL Datasourve as shown in
`Figure 1600 page 18
`
`The SQL Server must have the pubs sample database installed and it must be
`accessible by whatever user accoUnt you used in step
`above
`
`Step by step instructions for installing the samples included on the compact disc
`
`subdirectory called scripts from the Web root directory If you chose the
`Make
`default installation directory for Web Publishing Services your Web root directory is
`called wwwroot Within that directory create
`subdirectory called scripts
`From the command line this can be accomplished by
`
`md
`
`\wroot\script
`
`If you changed the Web root directory when you ran setup for the Internet Server use
`the path name you specified for the Web root in place of
`\wwwraot
`
`Copy Httpodbc .dll
`from the Internet Server installation directory to the
`The default installation threctoiy for Internet
`scripts directory created in step
`The Httpodbc d11 is located in
`\inetsrv
`Server software is
`
`subdirectory
`
`MSSUB EPIC
`000025
`
`Petitioner IBM – Ex. 1038, p. 22
`
`

`
`Mrosoft nemet swver ae
`Web Oatab$a ACOS eeas Notes
`
`912711995
`
`called seices From the command line this can be accomplished by
`
`COPY C\fletT\
`
`\bttpobcd11
`
`\root\ncript
`
`installation directory or the Web root directory
`If you changed the Internet Server
`when you ran setup for the Internet Server use the path you specified for the Internet
`inetsrv and
`\wwwroot
`Server and Web root in place of
`respectively
`
`Copy the sample files from the CD to the scripts directory From the command
`line this can be accomplished by
`
`copy
`
`v\wroot\cripta
`
`Again if you changed the Web root directory when you ran setàp for the Internet Server
`\wroot
`use the directory name you specified for.the Web root In place of
`
`file on the CD called copysamp.bat
`that you should not use This
`Note there Is
`reLease
`file will not properly copy the sample files for this beta
`
`Once the files are in the \Scripts directory and the ODBC data source Web SQL has
`been defined you can use the Internet Explorer to specify the following URLs to run the
`of this document
`examples shown in section
`httpky our server name/scripts/samplehtm
`
`httpIkyour server narne/scripts/sample2.htm
`hnpfIyour server name/scripts/sample3iiun
`
`MS-SUB EPIC
`000026
`
`Petitioner IBM – Ex. 1038, p. 23
`
`

`
`This Page is Inseited by IFW Indexing and Scanning
`Operations and is not part of lie Official Record
`
`BEST AVAILABIJE IMAGES
`
`Dcfectiv in1ags whhn this docuiiiut re accu rate rep CseRtatiun of t1ie origiua
`docu rneots submit ted by the applicnkt
`
`Defects in the images include but are not
`
`limited to the items checked
`
`BLACK BOKDLRS
`
`IMAGE CUT OFF Al TOP DOT IOM OR SIDES
`
`EAB ED TEXT OR DRAWING
`
`BLURRED OR ILLEGIBLE TEXT OR DrWINc
`
`SKEWED/SLANTED IMAGES
`
`COLOR OR BLACK AN1 WHITE PHOTOGRAPflS
`
`GRAY SCALE DOCUMENTS
`
`LINES OR MAPXS ON ORIGINAL DOCUMENT
`
`RE1EKENCE
`
`OR EXHIBIT
`
`SUBMITTED ARE POOR QUALITY
`
`OTHER
`
`______________
`_____
`IMAGES ARE BEST AVAILABLE COPY
`As resea net og thee ci octm menis will not con ect
`the ni age
`problems cheelced please do not report
`these problems to tie
`IFW Image 1tObleflI ailbox
`
`Petitioner IBM – Ex. 1038, p. 24

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket