Contents
-
Novell exteNd Director
-
Director subsystems
-
Director tools
-
Custom Web applications
-
J2EE 1.2 and 1.3 compliance
-
Workbench integration
-
Director wizards and editors
-
Application server and database support
-
Director project structure
-
EAR project structure
-
WAR project structure
-
Pieces of a Director application
-
Subsystem architecture
-
Subsystem archives
-
Subsystem deployment dependencies
-
How the subsystems register themselves with the framework
-
About the subsystems.xml file and the simulated classpath
-
How the subsystems access persistent data
-
How the subsystems access application resources
-
Role of a resource set in your application
-
What to put in a resource set
-
Subdirectories for resources and Java classes
-
Workbench projects for a resource set
-
Binding subsystems to a resource set
-
Configuring the resource set
-
Variables
-
General settings
-
Types and locations of resources: resourcePath, libPath
-
Directory keys for indexing
-
Dynamic loading of resources and classes
-
Using events to report resource set changes
-
Working with listeners
-
Types of events
-
What listeners do
-
Validating a resource set
-
Storing XML files that contain MBCS characters
-
About coding Java for Director applications
-
Using Java
-
Java platform support
-
About the core language
-
About APIs
-
Resources for learning Java
-
Using the Java APIs
-
Resources for learning J2EE
-
Using the Director API
-
Director API packages
-
Director API terminology
-
Director API reference documentation
-
Accessing subsystem services
-
Accessing a subsystem service by using a delegate
-
Getting a direct reference to a subsystem manager
-
About the Director tag libraries
-
Adding the JAR and TLD files to your project
-
Using a custom tag in a JSP page
-
About Struts
-
Understanding MVC
-
How Struts implements MVC
-
Example
-
Extending Struts with Director services
-
Business logic
-
Business process
-
Dynamic content
-
How to implement Struts with Director services
-
About error handling
-
Errors thrown by the Director API
-
Avoiding errors
-
Catching errors
-
Displaying messages
-
Displaying errors in the user's language
-
Logging information as your application runs
-
Uses for logging
-
What gets logged
-
Configuring the logs
-
Using logs in your application
-
Logging API
-
Getting a log
-
Setting the detail level
-
Adding messages to the log
-
Sample code for logging in a component
-
About the XML and IPDR logging providers
-
Working with XML templates
-
Working with IPDR templates
-
Built-in properties
-
Sample portal component using XML and IPDR logging
-
About configuring Director applications
-
Creating a new Director project
-
Reconfiguring your Director project
-
Changing the configuration
-
Adding subsystems
-
Removing or disabling subsystems
-
Adding a custom Web application to the project
-
Updating your Director project
-
Editing the configuration of a resource set
-
Using boolean variables in check box fields
-
Working with entries for resourcePath and libPath
-
Using resource set utilities
-
About the Relationship Viewer
-
Navigating relationships within a resource set
-
Creating a custom relationship analyzer
-
Creating a relationship analyzer class
-
About the Search tab
-
Searching a resource set
-
Saving a search as a view
-
Working with the Search API
-
Example: using the internal search template object
-
Example: creating your own search template object
-
Example: serializing a search request
-
About views
-
Displaying a view
-
Importing resources into a view
-
Exporting resources from a view
-
Defining custom views
-
About the view definition file
-
Searching for items within a resource set
-
Defining folders in a view
-
Including elements that are outside a view's resource set
-
Referencing other views within a view definition
-
About the Cache Coordinator
-
Configuring the Cache Coordinator
-
Running the Cache Coordinator
-
Recovering from a Cache Coordinator failure
-
Logging and debugging
-
About deploying a Director application
-
Deploying a Director EAR project
-
Basic deployment steps in Workbench
-
Defining a server profile
-
Deploying to the SilverStream and Novell application servers
-
Deploying to BEA WebLogic
-
Deploying to IBM WebSphere
-
Changing your deployment configuration
-
About the PAC
-
Accessing the PAC
-
Logging in to the PAC
-
Using the PAC
-
General
-
Logs
-
Cache
-
Cache Settings
-
Cache Holders
-
Cache Coordinator
-
Cache Statistics
-
About Director integration with Dreamweaver
-
Inserting Director component tags in Dreamweaver
-
Installing the Director extension for Dreamweaver
-
Inserting a component tag into a Dreamweaver page
-
Configuring Director to display PID pages from Content Management
-
addUserToGroup
-
createGroup
-
createUser
-
getGroupList
-
getResource
-
getUserID
-
getUserInfo
-
getUserList
-
getUserPreference
-
login
-
logoff
-
removeGroup
-
removeUserFromGroup
-
setUserPassword
-
userInGroup
-
userLoggedIn
-
About the Debug subsystem
-
How it works
-
Security considerations
-
Setting up the Debug subsystem
-
Running the Debug subsystem
-
Going to the Debug home page
-
Reporting on Director resources
-
Reporting on HTTP resources
-
Reporting on JNDI resources
-
Reporting on Director archive resources
Copyright © 2000, 2001, 2002, 2003 SilverStream Software, LLC, a wholly owned subsidiary of Novell, Inc. All rights reserved.