Novell Solutions on Sesame Street www novell com

Novell Solutions on Sesame Street www. novell. com Atiq Adamjee Senior Consultant Novell, Inc. AADAMJEE@novell. com Harold Moore Systems Engineer Novell, Inc hmoore@novell. com Guy Lunardi Solutions Engineer Novell, Inc. GLunardi@novell. com

Vision…one Net A world where networks of all types—corporate and public, intranets, extranets, and the Internet—work together as one Net and securely connect employees, customers, suppliers, and partners across organizational boundaries Mission To solve complex business and technical challenges with Net business solutions that enable people, processes, and systems to work together and our customers to profit from the opportunities of a networked world

Sesame Workshop—Who They Are • Sesame Workshop is a not-for-profit educational organization that stands alone in its ability to creatively solve major educational and developmental needs through effective uses of media that impact children around the world • Their mission: “To help children achieve their highest potential by creating innovative, engaging content that maximizes the educational power of media”

Sesame Workshop • Thirty-three years ago, Sesame Street was created to combat a critical need—kids in inner cities and disadvantaged neighborhoods did not have the basic skills needed to enter kindergarten • Sesame Street answered this call and revolutionized informal education, producing unprecedented results

Sesame Workshop • Today Sesame Workshop is a global fixture with three top PBS programs 4 Sesame Street, Dragon Tales, and Sagwa 4 Many other influential older kids programs 4 Sesame Street broadcast in 140 countries 4 20 co-productions that support educational across cultural diversities and issues 4 How we do it – – – Television/home video Radio Online and interactive platforms Books and magazines Educational products Community outreach needs

Sesame Workshop Ongoing Vision • Harness the power of the Sesame Workshop brand’s addressing the realities of children’s educational needs by 4 Building the foundation—the library of content to teach, enrapture, and grow children’s positive outlook toward the global community in which they live 4 Modeling and providing global sharing of resources, talent and knowledge around the creation of educational media 4 Transferring technology and knowledge in order for these efforts to be a lasting and measurable contribution to the ongoing education of all of tomorrow’s children

How Do We Build It? The Sesame Workshop Model • Production Funders public/private Research Distributor channels Content public/private w Need-based w Idea-driven w. Outcome-oriented Influentials (public policy, PK, MK, etc. )

Technology Strategy

Technology Strategy (cont. ) • Partnering with content and technology “solution providers” to enhance children’s access to Sesame Workshop content globally • Providing opportunities for technology companies to interact directly with content management and distribution models

Technology Strategy • Working directly with Novell on product development that supports 4 Content creation and management 4 Re-purposing and cross-purposing 4 Security 4 Access • Becoming the prototype for Novell to connect to tangible content distribution projects • Leveraging Novell and other technology partnerships

Novell and Sesame Workshop “A Technology Partnership” • Novell’s one Net—Sesame Workshop’s Global Village • Strategic portal development • Content and personalization across all distribution channels • • Internal and business clients Consumer site Digital receivers—PDA, home networking, digital satellite/cable etc. B 2 B opportunities • Singular desktop interface • CRM • Prototype model

Portal Strategy

Success Video

Products Used in the Novell Solution • Novell i. Chain® 2. 0 4 IO 122—Novell Secure Access: Overview 4 IO 121—Novell Account Management Introduction and • Novell Account Management 2. 1 Overview • Novell Portal Services 1. 5 4 IO 130—Extending Overview the Net: Novell Portal Solutions • Novell Dir. XML™ 1. 0 4 IO 118—Introduction • Novell Net. Ware® 6 4 IO 101—Net. Ware • e. Guide 4 IO 123—e. Guide to Novell Dir. XML Futures and Roadmap Introduction and Overview

Creating A Personalized One Net Experience • Novell is in the business of helping customer create one Net • An enterprise portal captures the vision of the one Net because a portal acts as a desktop or “Webtop” through a standard browser • Webtop provides employee with e-mail, in-boxes, calendars, corporate news, links to commonly used apps and folders and more • Access portal at home, at work, or one the road

Novell Portal Services • Very flexible and extensible 4 Simple solution to deploy 4 Platform-independent 4 Written to widely-used open industry standards such as XML, XSL, LDAP v 3, and HTTP

Delivering Dynamic Content • Dynamic content is what separates sophisticated enterprise portals from ordinary web pages • Most web pages are static 4 Content does not changes unless someone manually updates it • To provide dynamic content, you need an application that retrieves data at regular intervals 4 We call these applications “gadgets”

Demonstration My. Sesame. Workshop. net

Business Requirements For Portal • Scalability—hundreds today, millions tomorrow • Personalized content • Integration of web applications • File and information sharing • Distributed administration • End-user customization—“skin” selection • Public, restricted, and private communities

Novell Portal Services 1. 5 and Net. Ware 6 • Out of the box installation and no modifications necessary for default Apache and Tomcat installations • For enhanced performance 4 Set “—Xms. Xb –Xmx. Yb” in Tomcat startup file

Novell Portal Services 1. 5 and i. Chain 2. 0 • Create ISO object • From Novell Console. One®, create a guest account for i. Chain (e. g. , i. Chain. Guest. User) • Click on the New i. Chain Object icon located on the toolbar • Select i. Chain Service Object and name the object, e. g. ISO_OBJECT • Right click on the ISO_OBJECT and select Properties | General

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Browse for the Guest User and select the i. Chain. Guest. User 4 Click on Apply • Select the Protected Resource tab 4 Select Add and name the Resource (e. g. , Resource 1) • Give the URL prefix of the DNS name that is associated with the i. Chain Internet caching server (e. g. , http: //myportal. novell. com) • Apply the changes and close the Properties page

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Create Access Control Rule object • Click on New i. Chain Object icon and select i. Chain Access Control Rule • Name the Access Control Rule 4 E. g. , ISO_Access_Control_OBJ • Right click on the ISO_Access_Control_OBJ and select Properties | Resource • Select Add, add the Resource 1 that was just created in the ISO_OBJECT

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • The URL Postfix should be set to /* • Select the Apply tab • Add all contexts of any users that need to have access 4 Note: All contexts need to be specified as subcontainers will not be automatically given access • Click on Apply, close, and then close Console. One

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Start a web browser session and set the URL to http: //xx. xx. xx: 1959/appliance/config. html • Enter the user name and password and click OK • Click on Cache and then Access Control • Enter the ISO object name 4 E. g. , cn=ISO_OBJECT, ou=ichain, o=portal • Enter the LDAP Guest user name 4 E. g. , cn=i. Chain. Guest. User, ou=ichain, o=portal • Enter the LDAP IP address

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Enter the LDAP user name and password 4 This user should have admin rights • Click on Apply and then Refresh ACLCHECK • Click on Authentication and then Insert • Enter a profile name (e. g. , Profile 1) • Select the LDAP Authentication radio button and the LDAP Options button • Enter the LDAP IP address • Insert the contexts of the users for contextless login • Click OK, then OK again, then Apply

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Click on Web Server Accelerator and select Insert Select a name (e. g. , acc 1) • Enter the DNS name 4 This should match the DNS name of the i. Chain server, e. g. , myportal. novell. com • Insert a web server address 4 This should be the IP address of the NPS server • Check the public IP address of i. Chain server in Accelerator IP Addresses field • Select the Alternate Host Name and enter IP address of the portal server

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Check the Enable Authentication box • Select the Authentication Options button • Adjust Maximum Idle Time to an appropriate setting (e. g. , ten minutes) • Check Forward Authentication Information to Web Server 4 This passes the users’ login credentials from the i. Chain server to the NPS server for SSO • There should already be an existing profile (e. g. , Profile 1) 4 Select Add

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Setup SSLizer through this page by checking the Enable SSLizer box 4 This provides SSL communication between the browser and the i. Chain server • Click on OK, then OK again

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Click on the Management tab • Check Enable Pin List 4 This will tell the i. Chain server what not to cache 4 NPS creates dynamic pages based on the user logged into the portal 4 This content should not be cached by i. Chain • Select Insert and enter */nps/servlet/portal* • Select Pin Type to Bypass • Click on Apply

Novell Portal Services 1. 5 and i. Chain 2. 0 (cont. ) • Test the configuration by pointing the browser to the URL of the i. Chain server, e. g. , myportal. novell. com • When prompted by a Certificate Name check, click on Accept and then the default i. Chain login screen should appear • Enter the contextless credientials of a user that is in one of the contexts that was specified earlier • Click on Login 4 At this time you should now be successfully logged into both i. Chain and NPS

Novell Portal Services Custom Skins • Skins are located in 4 webappsnpsportalstylesheetsskins directory • Skins are built using the following files located in 4 webappsnpsportalstylesheetsskin_namedevi cesdefault • • INHERITABLE_AREA. XSL OBJECT_SCHEME. XSL BRANDING_AREA. XSL GADGET_FRAME. XSL LAYOUTSETTINGS. XSL SYSTEMMESSAGES. XSL CONFIGDATA. XSL

Novell Portal Services Custom Skins (cont. ) • Custom skins may be created by copying the XSL files in 4 webappsnpsportalstylesheetsskinsyour_skindevic esdefault directory

Novell Portal Services Skin XSL Files • BRANDING_AREA. XSL 4 Builds the Branding Area (header, body, and footer) 4 Responsible for passing control to the Inheritable Area template 4 Ensures that empty rows or cells are not created where not necessary 4 Prevents the header, body, and/or footer from being rendered to the Object Scheme when there are no gadgets assigned to one of those

Novell Portal Services Skin XSL Files (cont. ) • INHERITABLE_AREA. XSL 4 Builds the inheritable area, which can exist in two different modes • Paged • Non-paged 4 In paged mode, each object scheme will be shown as a page (Tab) on the screen • One object scheme at a time will be in focus or maximized 4 In a non-paged mode, it is responsible to build a header, body, and footer • Gadgets will be contained inside the inheritable area XML tag with their position and priority specified

Novell Portal Services Skin XSL Files (cont. ) • OBJECT_SCHEME. XSL 4 Builds the active/maximized object scheme/page 4 Responsible for arranging the gadgets inside the object scheme 4 Controls the column widths inside the body and whether the gadgets in the header and footer are stacked on top of one another or arranged horizontally left to right

Novell Portal Services Skin XSL Files (cont. ) • GADGET_FRAME. XSL 4 Responsible for defining the style of the gadget frame/title bar 4 Makes the call into the actual gadget stylesheet, which displays the gadget’s data

Novell Portal Services Skin XSL Files (cont. ) • LAYOUTSETTINGS. XSL 4 Test

Novell Portal Services Skin XSL Files (cont. ) • SYSTEMMESSAGES. XSL 4 Test

Novell Portal Services Skin XSL Files (cont. ) • CONFIGDATA. XSL 4 Test

Novell Portal Services Skin XSL Files (cont. ) • BRANDING_AREA. XSL • INHERITABLE_AREA. XSL • OBJECT_SCHEME. XSL • GADGET_FRAME. XSL • LAYOUTSETTINGS. XSL • SYSTEMMESSAGES. XSL • CONFIGDATA. XSL

Demonstration www. The. Letter. M. com

Typical Outlook Web Access Login

Web Access Authentication

Outlook Web Access Mailbox

Using i. Chain Secure Exchange

Using i. Chain Custom Login Page

Outlook Web Access Mailbox Secured Using i. Chain

i. Chain Cool Solutions Website • Entire solution outlined at 4 http: //www. novell. com/coolsolutions/icmag/feature s/a_sso_outlook_webaccess_ic. html

wi. N gear up, rope in, and climb on big with Novell Provisioning solutions pick up your entry card today at the Novell Provisioning table in the one Net solutions lab