throbber
3/13/2015
`
`Exploring the NetWare Web Server, Part3: A Complete lnnerweb Solution
`
`LOGIN
`
`United States. Engtis li
`
`CHANGE
`
`Products
`
`Services & Support
`
`Partners
`
`Communities
`
`About Novell
`
`How to Buy
`
`Exploring the NetWare Web Server, Part 3:
`A Complete lnnerweb Solution
`
`Articles and Tips: article
`
`ALAN MARK
`Corporate Integration Manager
`Systems Engineering Division
`
`01 Sep 1996
`
`Describes how to use the NetWare Web Server 2.5 along w~h Novell's lnnerWeb Publisher to set up a complete innerweb
`environment.
`
`~ Introduction
`~ Introducing Noven lnnerweb Publis her
`~ lnnerweb Concepts
`~ Setting Up the lnnerweb Environment
`~ Example: Alan's Exotic Trabel Company
`~ Conclusion
`
`Introduction
`
`Novell recently released version 2.5 of the NetWare Web Server and is including ~ w~h every copy of NetVVare 4.11 ("Green
`River"). The Web Server has also been bundled with a number of related tools to form a product called NovelllnnerWeb
`Publisher. This product is designed to give you everything you need to turn your existing NetVVare network into an Intranet.
`Whereas my previous two AppNotes dean wnh just the NetWare Web Server (version 2.0), I thought it would be useful to wa~
`until the release of version 2.5 and the lnnerWeb Publisher to continue the series. This way I can cover the other components
`included in lnnerWeb Publisher and show how they can be used along with the NetVVare Web Server to create a complete
`innerweb solution.
`
`Parts 1 and 2 of this s.eries provided a foundational overview of setting up a web environment, covering such topics as installing
`and configuring the web server, using graphics, and writing simple scripts. (See "Exploring the NetVVare Web Server" in the
`February 1996 issue and "Exploring the NetWare Web Server: Part 2" in the March 1996 issue of NoveHAppUcation Notes.)
`
`The outline for this third AppNote is as follows:
`
`Introduce the components of lnnerWeb Publisher, highlighting the new features in the NetWare Web Server version 2.5.
`
`Discuss some additional concepts relating to the use of NetVVare Web Server in an innerweb environment, specifically
`in regards to integration with the NetVVare operating system and services.
`
`Pull everything together by describing an example web site that demonstrates many of the ideas presented in all three
`AppNotes. You can download all of the sample files from the Systems Engineering Web Server at
`http:J/137.65.96.136:11111 .
`
`This AppNote is geared toward system administrators and "webmasters" who are looking for ideas on how to effectively
`Integrate an internal web environment into their existing NetVVare network.
`
`Before proceeding, let me clarify my use of the terms "innerweb" and "Intranet". Both words describe the same thing: a LAN that
`uses Internet protocols, such as HTTP (HyperText Transfer Protocol), to serve data. LAN clients receive data via an HTML
`(HyperText Markup Language) browser such as Netscape or Mosaic. I prefer the term "innerweb" to "Intranet" because it's
`less likely to be confused with the word "internet"--especiaHy in conversation.
`
`Introducing Novelll_n_ne_r_w_e_b_ P_ ub_l_is_h_e_r _________________________ _
`
`Novelllnnerweb Publisher provides tools to help you create and publish HTML documents on an innerweb or on the Internet.
`The package includes:

`
`NetWare Web Server 2.5
`
`NetWare 4.1 Runtime
`
`Netscape Navigator 2.01 (50-user license)
`
`Soflquad's HoT MetaL Lite (5-user license)
`
`QuarterDeck's I-Ware Lite, an IP-IPX Gateway (1 -server license)
`
`For more information on NetWare Web Server performance, see "NetWare on One Server Outperforms Wndows NT on
`Four CPUs" in the June 1996 is sue. and benchmark results from Shiloh Consulting at http://www.novell.com/.
`
`NetWare Web Server 2.5
`
`This second release of the NetWare Web Server has been optimized to take advantage of NetWare's superior file service
`engine. Besides being an ultra-fast HTTP server, version 2.5 supports the OS/2 name space, which means it now supports the
`downloading of Java applets. II runs as a NetVVare Loadable Module (NLM) under the NetWare 4.1 operating system.
`
`Another key feature of NetVVare Web Server 2.5 is its ability to browse Novell Directory Services (NOS) objects through any
`World Wde Web browser. A user can explore an organization's NOS tree and its objects from any innerweb or Internet
`connection, using the standard Web browser interface. We'll discuss this capability in more detail later in this AppNote. For now,
`
`htlps://support. novell.com/lechcenter/arti cles/ana19960901.html
`
`1/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 1
`
`

`
`3/13/2015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`suffice it to say that this is the first step in integrating Novelrs Directory with the World \Mde Web. Future plans call for an NDS(cid:173)
`to-LDAP (Lightweight Directory Access Protocol)· gateway, which will permit NOS users to perform directory functions on
`another directory service.
`
`NetWare 4.1 Runtime
`
`The NetWare Web Server software can be installed on any existing NetWare 4.1 server. But in case you want to create a
`dedicated innerweb server, lnnerWeb Publisher includes a runtime version of NetWare 4.1. This is a fully operational, two-user
`version of NetWare that acts as the base operating system for your innerweb server. The two-user license only applies to
`users actually logging in to the file server using NetWare Core Protocols (NCPs); you can have an un6mited number of users
`accessing the Web Server via HTTP.
`
`HoTMetaL Light
`
`SoftQuad's HoTMetaL Light is a web authoring toot that lets you create HTML documents
`without having to know all of those esoteric HTML commands. It supports the HTML 2.0 spec~ication, as well as many of the
`advanced HTML 3.0 and Netscape extensions. lnnerWeb Publisher includes both the 16-bit and 32-bit versions of HoT MetaL
`Light so you can run ft on \Mndows 3.1, \Mndows 95, or \Mndows NT workstations. I'll explain more about HoT MetaL when I
`discuss the example web site.
`
`Quarterdeck IWare Lite
`
`/.'
`
`I Ware
`IP{IPX
`
`!Ware is an IP-IPX Gateway that converts IPX packets Into IP packets , and vice versa. It
`resolves a prob1em many system administrators are facing as they expand· their LANs into intranets. Most NetWare networks
`use IPX as the standard protocol. However, you need TCP/IP to access web servers, and TCPIIP is more dMICult to administer
`and maintain than IPX. The solution is to use an IP-IPX gateway to eliminate the need for TCP/I P to ever reach the LAN.
`
`!Ware has both a client and a server component. On NetWare workstations, the IWare Client translates TCPIIP packets
`generated by a web browser into IPX packets . When these IPX packets arrive at the NetWare Web Server, the !Ware Server
`component (running as an NLM) converts them back into TCP/IP. From there, the packets are sent to the appropriate Web
`server, either within your own intranet or out on the pubtic Internet (see Figure 1).
`
`Figure 1: /ware acts as an IPX-to·IP gateway, translating IPX packets into TCP!IP packets to be sent to the appropriate web
`server, and vice versa.
`
`0 ini"M
`
`•
`
`IWare eliminates the need to install a TCPIIP stack on every client. Only one TCPIIP address Is needed for the NetWare 4.1
`server running the NetWare Web Server and the IWare Server component. Of course, you can continue to use TCPIIP on your
`workstations if you already have TCPIIP stacks loaded on them. \Mth NovelllnnerWeb Publisher, you can have any mixture of
`IPX and TCPIIP workstations on your intranet.
`
`Since TCPIIP packets are only forwarded to those clients which requested the data, IWare also acts as a "firewall" to the
`external Internet. Hackers cannot explore a LAN that uses !Ware as its TCP/IP router.
`
`N etscape N a vigator
`
`Nets cape is the leading web browser on the market. lnnerWeb Publisher comes with a 50-
`user license for Netscape Navigator version ix, which supports Java and JavaScript, as well as a variety of enhancements to
`HTML that make web pages better looking. Netscape's plug-in architecture allows third-party vendors to create modules which
`provides extra functionaHty, such as displaying animation and playing real-time audio within the browser.
`
`Most of the time and money expended on a web site goes toward keeping it operational and current. The ultimate goal of any
`web site is to have as many web pages as possible linked to real-time sources where content is updated automatically . Today ,
`the amount of true automation that you can implement is limited. unless you use sophisticated back-end database links and
`clever scripting. In the near future, technologies such as Java promise to make real-time information easier to provide in the
`web environment.
`
`Another goal for a web site is to provide links to existing data. Imagine being able to design an HTML document that integrates
`data residing on other NetWare servers, and that only allows access~ the user who requests the data has rights to that data.
`https:l/support.novell .com/techcenter/articles/ana 19960901.htm I
`
`2117
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 2
`
`

`
`3/13/2015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`Expanding on this concept, wouldn't ft be great if the links to the network data were dynamic, so that the underlying HTML
`document rarely needed to be updated?
`
`These types of implementations are possible with the NetWare Web Server, thanks to its ability to integrate with NetWare.
`Details on these and other concepts are provided in this section. Keep In mind, howev er, that some of the foftowing ideas are
`applicable only to innerweb env~onments, or to global internetwork solutions that route NOS services acro ss a WAN.
`
`Browsing NOS
`
`Wny would someone want to browse NOS objects? One big reason is that NOS is a real-time database that is the source of
`nearly all network information. Up-to-date user information such as phone numbers, addresses, and even photographs are
`available to anyone with a browser. No separate database Is necessary.
`
`Another attraction of this NOS browsing feature is the ability to explore any object. Suppose you have set up a network printer
`and named it "Printer1". Users who want to print to that printer have no indication from the name as to the printer's location. But
`W you were to store a GIF file representing a floor plan as part of the printer's object in NOS, users could browse the object to
`discover fts location (see Figure 2).
`
`Figure 2: The NetWare Web Server aHows you to store information about an object in NOS and then access that information
`from a standard web browser.
`
`Netscape: NOS Ob eel: .printerl.Dre_c_k --=---- ------
`~D
`~~~~~~~~~
`location: I http :I /137 .6~.96. \08 :80/nds/DRECK/D,-41-ck/printE>rl ?OP=Rud
`ooto 4• s~ ~~ovo~o~o'o~o~o~o~o~. o~oo"·~~~~~~7E~R7_~~--~========~---,~
`
`0020 00 00 00 00 00 00 00 00 00 00 00 00 . 00 00 00 00
`0030 00 00 00 00 00 00 07 00
`
`Revision
`
`• 15
`
`Home Page
`
`Photo GIF
`
`Floor pl!n lor 3rd le~el
`
`Men's
`
`Woman's
`
`Wth the VVEB_SNAP.OLL snap-in to the NWAdmin utility, you can store such things as photographs and home pages in NOS.
`The snap-in automatically extends the NOS schema to allow for the extra properties .
`
`Incorporating NetWare Filenames in a URL
`
`Suppose you are the network administrator for a department that has three NetWare fde servers. You want to implement a web
`server so that people in other departments can easily find and access your data. But you don't want just anyone looking at your
`department's files --only those who have rights to do so. NetWare's file system security will take care of the access control. but
`how do you point a web browser to files that exist on different NetWare servers?
`
`To answer this question, let's look at the structure of a UnWorm Resource Locator (URL), as illustrated in Figure 3.
`
`Figure 3: A URL is nothing more than a way to request a particular file on a host server.
`
`,...,
`"""·--
`,_,,!
`IUlpt/fw-w. Not..rn•)dlr-•')'f•ui.dit !>!"'-I'll~
`r
`
`!ia-fwl HutnCITAI
`
`Basically , a URL is just a fancy way of asking for data. It's not much different than asking for a file on a network drive. In DOS,
`a similar request looks like this:
`
`drive:\directory\filename (for example, F: \PUBLIC\EDLIN . COM)
`
`Using the Universal Naming Convention (UNC), a filename looks like this:
`
`//server/volume/directory/filename
`
`So in UNC. the name of a file in my home directory might be
`
`https://support.novell.com/techcenter/articles/ana 19960901.htm I
`
`3/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 3
`
`

`
`3/1312015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`Follow Novell
`
`Request a Call
`
`1-888-321-4272
`
`Print
`
`Feedback
`
`The FILE Protocol. You can encapsulate a UNC name within a URL, but to do so the URL requires a special "protocol" called
`FILE. The syntax for using FILE is similar to using HTTP, FTP (File Transfer Protocol), Gopher, and Usenet V'vhen the FILE
`protocol is used, the browser looks for a file or directory on a local or network file system.
`
`Here Is an example of a URL that points to an HTML file on the network :
`
`ile://1/skime/sys/alan/projects/current.htm
`
`where "skime" is the server name and "sys" is the SYS volume.
`
`A file reference within an HTML document might look like this :
`
`<a href="file:/1//skime/sys/alan/projects/current.htm"<<
`For current projects , click here .</a<
`
`This syntax is valid for a Wndows 95 or Wndows 3.x workstation running the NetWare Client 32 client software and Netscape
`v2.x. If the client is authenticated to the NOS tree, it will auto-connect to the file server. You do not have to map a drive prior to
`making the URL request
`
`For a Wndows 3.x workstation running the NetWare DOS Requester (VLM) client software, the URllooks like this :
`
`ile:///FI/alan/projects/current.htm
`
`where Fl indicates drive F. In this case, a drive mapping is required prior to the URL request
`
`Supporting Multiple Desktop Operating Systems. For other types of NetWare clients besides DOS/\Mndows, the proper
`URL syntax is determined by how the desktop operating system interprets the server and volume name. For instance, on my
`Macintosh the URL for the file referenced above looks like this:
`
`file:///SKIME.SYS/ALAN/PROJECTS/CURRENT.HTM
`
`In the MacOS, server and volume names are combined into one desktop reference ("skime.sys"). Note also that the r;e iS only
`accessible W the user is currently attached and authenticated to file server Skime.
`
`For non-DOS filenames, spaces and non-standard characters are converted to their hexadecimal equivalents (for example,
`"%20" for space). For example, when I choose the "Open file ... " option in my Macintosh web browser and select a local file, the
`URL is displayed as follows :
`
`ile:///Macintosh%26HD/Data/Novell%26%C4/NOVLOG1.GIF
`
`Since many people find this extra clutter confusing, H's best to use only numbers and letters for file and directory names.
`
`V'vhen supporting diverse desktop operating systems, you may need to provide muttiple references to the same physical
`location. lnftial HTTP requests to the server would include the browser type and client OS, found in the environment variable
`HTTP _USER_AG ENT. For example:
`
`HTTP_USER_AGENT = Mozilla/2.02 (Macintosh; I; PPC)
`
`A script could then return a properly-syntaxed URL corres ponding to the client platform detected in this environment variable.
`Here is a slice of Peri code that would perform this function :
`
`$user_agent = "$ENV{'HTTP_USE R_AGENT}";
`
`if ($user_agent
`
`/Mozilla/ ) {
`
`#** Netscape
`
`if ($user_agent =~/Macintosh/)
`
`#* * using Macintosh **
`
`$url = "file:///SK I ME.SYS/ALAN/PROJECTS/CURR ENT . HTM";
`
`elsif ($user_agent = ~ /Win16/)
`
`#** using Windows 3. 1**
`
`url$ = "file:///FI/alan/projects/current.htm";
`
`elsif ($user_agent =- /Win32/)
`
`#** using Windows 95**
`
`https://support.novell.com/techcenter/articles/ana 19960901 .htm I
`
`4/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 4
`
`

`
`3/13/2015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`$url
`
`"f ile:/1//skime/sys/alan/projects/current.htm";
`
`Unfortunately. it is impossible to automatically determine network client she I information (VLM or Cfient32) from an HTTP
`request. The method shown above only works if you know that all workstation types are running the same NetWare client
`software; for instance, that all Wndows 3.1 workstations are running the VLM client.
`
`Using Directory Map Objects for Dynamic Links
`
`One of the biggest headaches in maintaining a web sne is making sure that hypertext links--those references that specify other
`documents or locations --are valid. V'vtlen the document referenced by a hypertext fink is moved or deleted, you see this all-too(cid:173)
`fam~lar error message:
`
`404 Not Found The requested URL /LONGF/LO.HTM was not found on this server.
`
`Changes to hypertext links affect browser bookmarks, scripts, and HTML files . In other words, they affect users and
`administrators alike.
`
`Since NOS is a real-time database, ij lends itseW well to storing key link information. In fact, NOS already provides an object that
`fits the bill quite nicely: the Directory Map object.
`
`Background on Directory Maps. Directory Map objects have been around since the release of NetWare 4.0 in 1993. The
`purpose of these objects is to store pointers to directories on any server on the network, and allow names to refer to server
`directories. Directory Maps are normally used in login scripts, batch files, and MAP commands . They use simple names instead
`of whole paths. For example, using a Directory Map object, the MAP command
`
`IMAP J:=APPSERVER/APPS:WORDPROC/WPGe
`
`becomes
`
`IMAP J :=WORDPERFECT
`
`This simplified MAP command is then placed in users' login scripts and batch files. V'vtlen the site upgrades from WordPerfect
`6.0 to 6.1, all the administrator has to do is update the Directory Map object to point to
`"APPSERVER/APPS:WORDPROCMP61". No changes need to be made to the users' login scripts or batch fffes. Best of all,
`the users don't have to know the directory structure on the server.
`
`Using Directory Maps for URls. Applying this concept to the web, a Directory Map object can be referenced as a URL. That
`way, whenever a reference changes, you only need to update one object in NOS. The syntax is:
`
`rile:////tree/Org/OU/DMap
`
`where treeis the NOS tree name, Orgis the Organization, OU is the Organization Unij, and DMap is the Directory Map object
`name. For example, to reference fdes in the •wordperfect" directory on an application server, the URL might be:
`
`file://1/oak/skigreat/downhillers/wordperfect
`
`Note: This syntax is valid only for Wndows 95 or Wndows 3.xworkstations running NetWare Cient 32 and Netscape v2.x.
`
`Remember that the referenced data is only accessible if the user is currently authenticated to tree "oak" and to server
`"appserver." There is no need to have a drive mapped to the server.
`
`Another advantage to using NOS Directory Map objects as web references is that you can authorize specific users to change
`those objects without giving them rights to change the base web documents (which should be controlled by the web
`administrator). This scenario also relieves the web administrator from having to manage those references.
`
`To have a user control a Directory Map, simply make the user a trustee of the object with property rights RV'£ (read, wrne,
`compare) to the Path property . If you grant the user Supervisor rights, he or she will be able to delete the Directory Map object.
`
`Note: Currently , the URL syntax requires using the FILE protocoi.Therefore, you cannot specify scripts or Server Side
`Includes (SSis)as· documents. In the future. complete URLs will be stored in NOS sothat any location or document type can
`be referenced.
`
`Enabling NOS Browsing
`
`\Mth the NetWare Web Server, the NOS browsing capability is turned off by default. You enable it by launching the WEBMGR
`utifity, specifying which server to access, and clicking on the "Enable NOS browsing" button. A tine is created in the
`SYS:WEB/CONFIG/SRM.CFGfile that reads:
`
`LoadableModule /nds/ sys:web/docs/cgi/ndsobj/ndsobj.nlm
`
`You must restart the HTTP process in order for the changes to take effect.
`
`To store images and home pages in NOS. the NWAdmin utility must load WEB_SNAP.DLL when it starts. This is done by
`adding a line in the NWADMIN.INI file that looks something like this (depending on where the DLL was installed):
`
`Object DL Ls]
`ebsnap = c:\netware\web_snap .dll
`https://support.novell .com/techcenter/articles/ana19960901 .htm I
`
`5/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 5
`
`

`
`3/13/2015
`
`Exploring the NetWare Web Server, Part3: A Complete lnnerweb Solution
`
`The first time you load NWAdmin with the snap-in, a dialog box appears asking if you want to extend the schema to support the
`additional properties as sociated with NDS browsing. Clicking "OK" extends the schema. (Once the schema is extended , the
`added properties cannot be removed.)
`
`Storing Images with an NDS Object. Once NDS Browsing is enabled and the schema is extended, you can store images
`and other helpful information as part of your NDS objects . As an example, here is how to store a reference to a user home page
`and a photograph (saved as a JPEG file) in a person's NDS User object.
`
`1. In NWAdmin, select a user by double-clicking on the User object.
`
`2. Scroll down in the list of configuration pages at the right until you see the "Home Page and Photo Attributes" tab. Click
`on it to open a page similar to the one shown in Figure 4.
`
`Figure 4: In NWAdmln, you can specify a home page and a photo for NOS User objects.
`
`iii Useo-: ~dlk
`
`-
`
`11ome Page and Photo Attributes
`
`dome i>ag
`
`1 "&llll~~t nmi.."I'1J!!;:. I I 8,eiJ.{~II'IJ;J£.f.i!!i I
`
`fila !tilno~
`
`II TN
`I
`
`PI'!Uitl
`
`I
`
`I
`
`ll
`
`Select. Photo
`
`I
`
`I ~w;ii.fmt_o I
`
`I
`
`I
`I
`
`-
`RiglilsT o Files and ·
`DirectorieS
`
`Group Membeothip
`
`It:!
`
`~~
`
`~ .
`ttl
`
`Secw~y Equal To
`
`Postal Addoes.
`
`J
`Accour~ Balance -l'
`SeeA!s~ - ~L
`Home Page and Photo
`~
`~.ttiibutes
`
`lj l
`
`.':
`
`;
`
`>Gif file""""~~'
`
`IF:\IJSERS\AMARK\PUBLIC.'MMMAMARK.GIF
`
`Gooup\llr.e
`
`I ~~!rn "C
`
`la~<her Confi!JO!a.tioo
`
`r
`
`3. C6ck on "Select HTML file" to store a web page reference in NDS. Any references within this HTML file must be a
`complete URL wah the full path. In other )YOrds, you can't use relative references (specifying a filename wah no path).
`For example, ~you wanted to include a banner image in the HTML file, you would specify tt like this :
`~img src = "/images/banner.gif"<
`
`where the "images" directory is located under sys:webldocs on the webserver.
`
`You can also specify images from a user's home web directory like this :
`
`~img src = "/-username/graphic .gif"<
`
`4. CUck on "Select Photo" to store an image in NDS. Type the full path and filename in the "GIF F~e Name" field. Although
`the defautt file type is GIF, you can store another graphic type such as JPEG.
`
`Now when your innerweb users browse an NDS user, an initial screen wiM be displayed showing key user properties and the
`user photo. along with a link to the user's NDS home page. Detailed user information is available when another icon is clicked
`(see Figure 5).
`
`Figure 5: When an NOS User object is browsed, an initial screen such as this one is displayed.
`
`https ://support. novell.com/techcenter/arti cl es/ana19960901.htm I
`
`6/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 6
`
`

`
`3/1312015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`~i"< Netscape • (NDS Dbtect. .Koli.Dreck HomePage)
`
`-
`
`l!lfiJ
`
`Joe Kofi, l\!Ir.
`
`Information:
`Department. T<avel
`Location: Vunderland
`Phone Number: 801-429-1000
`Fa'tNumber: 801-429-1001
`
`Sec Joe's Home Page
`
`The NetWare Web Server also provides a way to directly access NOS objects and properties . For example, the URL lo read a
`user's home page stored In NOS is:
`
`http://webserver/nds/tree/Org/OU/User?OP=Read&ATTR=Home_Page
`
`Refer to the NetWare Web Server documentation for more details on this syntax,
`
`User Home Pages
`
`As discussed in Part 1, users can create customized home pages and store them In their home directories. 'Mth this new
`release of the NetWare Web Server, you can choose to store the user's main home page in NOS rather than in the user's home
`directory, The advantage of using NOS Is that the home page can be referenced by any web server on the network. The
`disadvantage is that the user must use NWAdmin to upload the HTML file to NOS. However, if few changes are made to the
`main page, that's not much of a worry.
`
`The standard way to access a user home page is to specilly the URL using the following syntax:
`
`tTTP:/Jservername/~username
`
`User home web directories can also be referenced by an Alias object. For example, ff the object named "GreatOne" is an alias
`of User object "Alan," the home web directory can be specified by either HTTP://servemame/-alan or
`HTTP://servemame/-greatone.
`
`Note: Remember that, to access a user's home web directory via HTTP, theNetWare Web Server software must be installed
`on that server.
`
`Here's a final tip: If you have a dedicated web server and you want to support user home pages, consider applying space
`limitations for each user. Most online services restrict the size of user data areas, and NetWare can do the same via the
`NWAdmin utility (see Figure 6).
`
`Figure 6: Set volume space restrictions in NWAdm/n to limit how much disk space users can use.
`
`https://support.novell.comltechcenter/arti cles/ana 19960901.htm I
`
`7/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 7
`
`

`
`3/1312015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`:iearch ConteKI:
`I Alantest.SED.SERVICES.tlovell
`0 Search !;_ntire Subtree
`
`User:
`
`alan.Aiantest.SED.SERVICES.IIovell
`
`Volume Space Used Dy User; 0 K
`
`[81 !.imited Volume Space
`Volume ~ace Limit (Kb):l '-2_o_oo _______ ___J
`
`~ IJ Cancel J I !!elp
`
`Space restrictions are set by volume. Currently, a home web directory can be separate from a normal home directory only if
`the web server is in a different NDS tree. (This lim~ation will be removed in a future release.)
`
`Setting Up the lnnerweb Environment
`
`Before we look at out example web site, let's review the basic steps necessary for setting up an innerweb environment. You
`can us e this as a checklist to ensure that your own site is ready. For more detail, refer to the NetWare Web Server
`documentation.
`
`1. Verify that the server has enough RAM and disk space to accommodate the increased demand for data. If this server
`will be heavily used, install high-speed LAN and disk adapters. Remember that each HTTP client can establish several
`(usually up to four) slmu~aneous connecllons to the server.
`
`2. Install TCPnP support on the serYer. Use the INETCFG.NLM utility for menu-driven operations .
`
`3. Install the OS/2 (HPFS) name space support for long filenames . This willslighlly increase server memory and storage
`requirements, but~ will allow for a more flexible file naming system. \Mth long file name support loaded, files must be
`referenced by their long names (if they have one). Be aware that not all WWWtools or script interpreters support long
`file names, whereas others (such as Java applels) require them.
`
`4. If data will be accessed from the web server using the FILE protocol, the server must have sufficient user licenses,
`and the users must be authenticated to NDS before data is reques ted . (Standard HTTP requests do not take up any
`NetWare user connections. You simply need to ensure that your servers can be accessed via IPX and TCPnP
`throughout the LAN and WAN.)
`
`5. Install the NetWare Web Server software. (Basic guidelines are given In "Exploring the NetWare Web Server" In the
`February 1996 issue. For more detailed information, refer to the Novell product documentation.)
`
`6. From any browser, verify that the web software is working by accessing HTML documents. Execute the sample Peri
`scripts and Server Side Include documents as well.
`
`7. If needed, change the default settings for authorization and processing via the Web Server Administration utility
`(V\£BMGR).
`
`One change we'll need for the example is to enable SSI on all directories. You dO this in V\£BMGR by selecting the
`DOCS directory and clicking on "Enable Includes" (see Figure 7) . This enables SSIIo work for any file with a .SSI
`extension in a directory under /WEB/DOCS. II also allows SSI in our home page, which is especially useful for things
`like page hit counters .
`
`8. Enable user home pages. This is done by clicking "Enable user documents" under the Server tab in WEBMGR .
`
`9. If desired, edit the options in the SYS:WEB/CONFIG/SRM.CFG file .
`
`For instance, to change the default horne page document name from INDEX.HTM to INDEX.SSI, modify the Directory
`Index entry to read:
`
`~irectoryindex index.s~i
`
`10. Extend the NDS schema to include HTML documents and images as user properties . V\£B_SNAP.DLL does this the
`firs t time~ is loaded, asexptained earlier in this AppNote.
`
`Figure 7: The "Enable includes " option in WEBMG R enables Server Side Includes.
`
`https://support. novell .com/techcenter/articles/ana19960901.html
`
`8/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 8
`
`

`
`3/13/2015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution
`
`=I
`
`NetWare Web Server
`
`Sewer
`
`Directories I User Access
`
`Logs
`
`I
`
`S~;3 tem Acce~~
`
`Existing directories:
`docs
`localhosl: 8001 /scripts
`localhost:8002/sys:web/scripts/perl
`localhost:8003/sys: web/samples/cgiapp
`maps
`docs/images
`..... "' .... -/,..,.;
`
`J• Browse... I
`
`~Index options
`
`J ()(. Fancy indexing
`
`i
`
`I
`
`Directory path:
`jdocs
`
`Contains:
`!Documents
`
`Features
`
`~
`
`~e_i!!.r:l.~i!!.!!_
`• Icons are links
`~~~~~~4~ I l! .!F .li!O!~!!J!!!~-=-
`1 Add
`I 1r Clian!)e
`I li Flemove
`
`rx:_x_
`
`Example: Alan's Exotic Travel Company
`
`-
`
`--=·
`
`You can download this entire example, including scripts, images, and HTML documents, from Novelfs VWWVserver at
`http://yfflw.noveft.com/.
`
`This innerweb example is based on an in-house travel service. Alan's Exotic Travel Company (TraveiCo) is a subsidiary that
`serves the needs of a medium-sized organization. Its customers are the company's employees. In addition to arranging all
`business travel, TraveiCo generates extra revenue by selling exotic trips to the employees. T hus they want to increase
`employee awareness of this lesser-known personal travel service.
`
`TraveiCo already has several NetWare 4.1 serv ers that are used for different purposes . The most important of these is the
`master travel database which stores all employee travel information, such as travel histories and frequent flyer preferences.
`
`TraveiCo has identified five main reasons for wanting to create an innerweb site:
`
`1. To disseminate information regarding exotic travel journeys, using attractive techniques such as photos , videos, and
`animation clips.
`
`2. To allow employees to tap into their travel history without having to call a travel agent.
`
`3. To coordinate with the personnel department to provide accrued vacation time per employee. This information is
`confidential, but it helps employees make vacation plans.
`
`4. To allow previous exotic travellers to store travel photos, comments, and tips in their own personal web directory
`(limited to 2MB total data size) .
`
`5. To allow any web user to browse TraveiCo's NDS tree and view each travel agent's photo and HTML page.
`
`They want to design their web site around the following main areas:
`
`Exotic journeys. Provide a way for employees to search for exotic trips by clicking on locations from a world map. A
`search engine displays related documents , which the user can select by the cflck of a mouse.
`
`Client travel database. Allow valid NDS users to view their own personal travel data, including flying preferences and
`previous journeys taken.
`
`Client travel p hotos. Allow any user to browse client information stored in NDS, including photographs, home pages,
`and user information s uch as phone numbers. Also and go to the user's home web directory.
`
`Contests and promotions. Entice users to return often by offering a game with prizes for the winners. Also provide a
`dynamic link to current promotion information via NDS.
`
`Organizing the Web Site
`
`https:l/support.novell .com/techcenter/arlicl es/ana 19960901.htm I
`
`9/17
`
`BLUE COAT SYSTEMS - Exhibit 1059 Page 9
`
`

`
`3/1312015
`
`Exploring the NetWare Web Server, Part 3: A Complete lnnerweb Solution

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