Previous Contents Index Next |
iPlanet Portal Server: Mobile Access Pack Programmer's Guide |
Chapter 8 Attributes and Schemas
This chapter discusses the attributes used by the Mobile Access Pack:These attributes are stored in the iPlanet Portal Server profile service. The attributes discussed in this chapter can be modified from the command line and also from the administration console graphical user interface. Please see Appendix B "Sample Tasks" for more information on modifying these attributes.
The following HTML channel attributes are used by the server components to configure a channel for HTML clients only.
The following is an example of the <channelName>-description attribute. This attribute stores the user-visible description of the channel. This description is displayed in the Content page.
<iwt:Att name="<channelName>-description"
<Val>Component description</Val>
The following is an example of <channelName>-backgroundColor attribute. This attribute stores a valid HTML background color value for the channel window. HTML color values can be specified as a literal string which is the color's actual name (for example, aquamarine) or as a hexadecimal triplet (for example, #7FFFD4).
<iwt:Att name="<channelName>-backgroundColor"
The following is an example of <channelName>-hasHelp attribute. This attribute specifies whether or not the channel has end-user help available. A value of true indicates that the channel has help content and a value of false indicates that the channel does not include help. This is used to determine whether or not to display the help icon (?) on the channel.
<iwt:Priv name="<channelName>-hasHelp"
The following is an example of the <channelName>-helpLink attribute. This attribute stores the path to the component's help page for a html client. The path must be relative to <servername>:<portnumber>/help/<locale>.
<iwt:Att name="<channelName>-helpLink"
<Val>http://<servername>:<port>/help/<locale>/ComponentTOC.html</Va l>
The following is an example of the <channelName>-column attribute. This attribute specifies the column in the desktop page where the channel will be displayed. Typically, the column width can be thin-thick (value not required), thick-thin (value not required), thin-thick-thin (value of 1 indicates leftmost column and value of 2 indicates rightmost column, and the thick width does not require a value), thin-thin-thin (value of 1 indicates leftmost column, value of 2 indicates the rightmost column, and value of 3 indicates the center column).
<iwt:Att name="<channelName>-column"
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
<Wperm>ADMIN</Wperm><Wperm>OWNER</Wperm>
The following is an example of the <channelName>-row attribute. This attribute specifies the the vertical ordering or positioning of the channel in a column. If conflict arises (as a result of more than two channels requiring the same position), the order in the channel list is used.
<iwt:Att name="<channelName>-row"
The following is an example of the <channelName>-width attribute. This attribute specifies the width of the channel. A channel can be thin, thick, occupy the width of the desktop at the top (full_top) or botton (full_bottom).
<iwt:Att name="<channelName>-width"
The following is an example of the <channelName>-editType attribute. This attribute specifies the type of edit page that will be returned for the channel. The acceptable values are:
edit_complete - Indicates that it will return a complete HTML page.
edit_subset - Indicates that it will return a subset of an HTML page that will be further wrapped by a template to add things like bordering, sumbit buttons, etc.
The following is an example of the <channelName>-isEditable attribute. This attribute specifies whether or not the channel is editable from the user's desktop. This is used to determine whether or not to display the edit icon on the channel. This is also used to control access to configuring the channel; that is, a value of false will not permit the user to configure or edit the channel setup from the user's desktop.
<iwt:Priv name="<channelName>-isEditable"
The following is an example of the <channelName>-hasFrame attribute. This attribute specifies whether or not the channel contains a frame (see iPlanet Portal Server 3.0 Service Pack 3a Release Notes for more information on setting up framed and frameless channels).
<iwt:Att name="<channelName>-hasFrame"
The following is an example of the <channelName>-isMovable attribute. This attribute specifies whether or not the channel can be moved in the desktop (see iPlanet Portal Server 3.0 Service Pack 3a Release Notes for more information on locking a channel's position on the desktop).
<iwt:Priv name="<channelName>-isMovable"
The following is an example of the <channelName>-isMinimizable attribute. This attributes specifies whether or not a channel can be minimized in the user's desktop. This is used to determine whether or not to display the Minimize icon on the channel.
<iwt:Priv name="<channelName>-isMinimizable"
The following is an example of the <channelName>-isMinimized attribute. This attribute specifies whether or not the channel will be displayed as just a title bar on the desktop that the user can maximize.
<iwt:Att name="<channelName>-isMinimized"
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
<Wperm>ADMIN</Wperm><Wperm>OWNER</Wperm>
The following is an example of the <channelName>-isRemovable attribute. This attribute specifies whether or not the channel can be removed from the desktop. This is used to determine whether or not to display the Remove icon on the channel.
<iwt:Priv name="<channelName>-isRemovable"
The following is an example of the <channelName>-isDetachable attribute. This attribute specifies whether or not the channel can be detached from the desktop into a smaller pop-up window. A value of true indicates that the channel is detachable and false indicates that the channel is non-detachable.
<iwt:Priv name="<channelName>-isDetachable"
The following is an example of the <channelName>-isDetached attribute. This attribute specifies whether the channel will be displayed detached from the desktop as a pop-up window.
<iwt:Att name="<channelName>-isDetached"
The following is an example of the <channelName>-hasBorder attribute. This attribute specifies whether or not the channel has a border. A true value indicates that the channel has a border and false value indicates that the channel has no border.
<iwt:Priv name="<channelName>-hasBorder"
The following channel attributes are used by the Mobile Access Pack components to configure a channel.
The following is an example of the <channelName>-title attribute. This attribute stores the name or title of the channel. This is the user visible channel title. This title is displayed on the channel and in the Content page.
<iwt:Att name="<channelName>-title"
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
The following is an example of the <channelName>-clientHelpLinks attribute. This attribute stores the path to the client specific help for the component or channel.
<iwt:Att name="<channelName>-clientHelpLinks"
<Val>clientType|Path_to_help_file</Val>
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
<Wperm>ADMIN</Wperm><Wperm>OWNER</Wperm>
Each clientType listed here must exactly and accurately match the clientType that is found in the Client Data. Specify only one file (such as ComponentTOC.html or a higher level table of contents with links to more files if needed) per component in this attribute. The path to the help file must be relative to <iPS_install_base>/SUNWips/public_html/docs/<locale>/online_help.
The following is an example of the <channelName>-refreshTime attribute. This attribute specifies the amount of time, in seconds, until the channel content, cached by the desktop, expires. When the user refreshes the desktop page, the Desktop checks each channel to see if the refresh time (specified in this attribute by each channel) has elapsed since the channel's content was cached. If the time had not elapsed, then the Desktop builds its page using a cached copy of the channel's content. If the cache expires, then the Desktop fetches fresh content from the channel.
<iwt:Att name="<channelName>-refreshTime"
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
The following attributes reside in the profile component iwtCalendarProvider.
iwtCalendarProvider-calendarUserName
The following is an example of the iwtCalendarProvider-calendarUserName attribute. This attribute's value can be specified from the edit Calendar page on the user's desktop. This attribute stores the user's calendar server id and is used to connect to the calendar server.
<iwt:Att name="iwtCalendarProvider-calendarUserName"
iwtCalendarProvider-calendarUserPassword
The following is an example of the iwtCalendarProvider-calendarUserPassword attribute. This attribute's value can be specified from the edit Calendar page on the user's desktop. This attribute stores the user's calendar server password and is used to connect to the calendar server.
<iwt:Att name="iwtCalendarProvider-calendarUserPassword"
iwtCalendarProvider-calendarServerName
The following is an example of the iwtCalendarProvider-calendarServerName attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the calendar
This attribute stores the user's calendar server name and is used to connect to the user's calendar server.<iwt:Att name="iwtCalendarProvider-calendarServerName"
iwtCalendarProvider-calendarServerPort
The following is an example of the iwtCalendarProvider-calendarServerPort attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the calendar client
This attribute stores the user's calendar server port number and is used to connect to the user's calendar server.<iwt:Att name="iwtCalendarProvider-calendarServerPort"
The calendar channel uses the servername, port number, username and password set by the user in the edit page and stored in the iwtCalendarProvider-calendarServerName, iwtCalendarProvider-calendarServerPort, iwtCalendarProvider-calendarUserName, and iwtCalendarProvider-calendarUserPassword attributes respectively to connect to the calendar server and get the events.
The following is an example of the iwtCalendarProvider-weekView attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the calendar
If set to true, the calendar displays a weekly view of events. By default, this is set to true.<iwt:Att name="iwtCalendarProvider-weekView"
The following is an example of the iwtCalendarProvider-dayView attribute. This attribute gets its value:
From the Administration Console at the time of configuring the channel for the calendar client
If set to true, the calendar displays a daily view of events. By default, this is set to true.<iwt:Att name="iwtCalendarProvider-dayView"
The following is an example of the iwtCalendarProvider-clientURL attribute. This attribute's value can be specified from the administration console at the time of configuring the channel for the calendar client or by using the ipsadmin command (see "Configuring the Attributes").
The server URL to build the Single Sign On link is configured in this profile attribute. This attribute uses a stringlist to store the clientType and the client specific server URL for that clientType. If the clientType is not found in the session, then the calendar channel defaults it to genericHTML. The channel iterates through the list of values from this attribute and gets the clientURL corresponding to the clientType accessing the calendar server.
<iwt:Att name="iwtCalendarProvider-clientURL"
<Val>genericHTML|INST_CALENDAR_CLIENT_URL</Val>
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
iwtCalendarProvider-jspLocationLength
The following is an example of iwtCalendarProvider-jspLocationLength attribute. This attribute specifies the number of characters to display about the event location on the corresponding client. This is only applicable to clients that utilize the calendar JSP template files (discussed in "iPlanet Calendar Server JSPs").
<iwt:Att name="iwtCalendarProvider-jspLocationLength"
desc="Length of Event Location to Display Via JSP"
iwtCalendarProvider-jspDescLength
The following is an example of iwtCalendarProvider-jspDescLength attribute. This attribute specifies the number of characters to display about the event description on the corresponding client. This is only applicable to clients that utilize the calendar JSP template files (discussed in "iPlanet Calendar Server JSPs").
<iwt:Att name="iwtCalendarProvider-jspDescLength"
desc="Length of Event Description to Display Via JSP"
iwtCalendarProvider-jspSummaryLength
The following is an example of the iwtCalendarProvider-jspSummaryLength attribute. This attribute specifies the number of characters to display about the event summary on the corresponding client. This is only applicable to clients that utilize the calendar JSP template files (discussed in "iPlanet Calendar Server JSPs").
<iwt:Att name="iwtCalendarProvider-jspSummaryLength"
desc="Length of Event Summary to Display Via JSP"
iwtCalendarProvider-jspEventNumLines
The following is an example of the iwtCalendarProvider-jspEventNumLines attribute. This attribute stores the number of calendar events to display on the corresponding client. This is only applicable to clients that utilize the calendar JSP template files (discussed in "iPlanet Calendar Server JSPs").
<iwt:Att name="iwtCalendarProvider-jspEventNumLines"
desc="Number of Events to Display Via JSP"
The attributes discussed in Table 8-4 reside in the profile component iwtMailProvider.
The following is an example of the iwtMailProvider-msgCopyInSent attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the mail client
This attribute indicates whether or not to save a copy of the message in the user's Sent folder. By default, this is set to true.<iwt:Att name="iwtMailProvider-msgCopyInSent"
desc="Place a copy of message in Sent"
The following is an example of the iwtMailProvider-clientURL attribute. This attribute's value can be specified from the administration console at the time of configuring the channel for the mail client and/or from the Edit Mail channel page.
The server URL to build the Single Sign On link is configured in this profile attribute. This attribute uses a stringlist to store the clientType and the client specific server URL for that clientType. If the client type is not found in the session, then the mail channel defaults it to generic HTML. The channel iterates through the list of values from this attribute and gets the client URL corresponding to the clientType accessing the mail server.
<iwt:Att name="iwtMailProvider-clientURL"
<Val>genericHTML|INST_MAIL_CLIENT_URL</Val>
The following is an example of the iwtMailProvider-clientPort attribute. This attribute stores the port number of the mail client.
<iwt:Att name="iwtMailProvider-clientPort"
The following is an example of the iwtMailProvider-sortOrder attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the mail client
This attribute indicates the order in which to sort the user's messages in the inbox for display. The user can either view the most recent at the top or at the bottom. By default, the most recent message are displayed at the top of the inbox.<iwt:Att name="iwtMailProvider-sortOrder"
iwtMailProvider-displayHeaders
The following is an example of the iwtMailProvider-displayHeaders attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the mail client
This attribute indicates whether or not to display the message headers in the user's mail channel. By default, this is set to true.<iwt:Att name="iwtMailProvider-displayHeaders"
The following is an example of the iwtMailProvider-numberHeaders attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the mail client
This attribute indicates the number of message headers to display in the user's mail channel. By default, up to five message headers are displayed in the user's mail channel and the channel limits the maximum number of message headers to be displayed to 30.<iwt:Att name="iwtMailProvider-numberHeaders"
iwtMailProvider-predefinedReplies
The following is an example of the iwtMailProvider-predefinedReplies attribute. This attribute's value can be specified from the edit Mail page on the user's desktop and/or from the Administration Console. This attribute allows the user to create and store messages to send out later, typically, from the mobile device. The predefined messages cannot exceed thirty characters. Although these messages can be set up from the Administration Console as well, these messages must be created by the user from their edit Mail page.
<iwt:Att name="iwtMailProvider-predefinedReplies"
The following is an example of the iwtMailProvider-signature attribute. This attribute's value can be specified from the edit Mail page on the user's Desktop and/or from the Administration Console. This attribute allows the user to create and store a signature from the user's Desktop. Although this can be set from the administration console as well, this must be set by the user from the edit Mail page.
<iwt:Att name="iwtMailProvider-signature"
iwtMailProvider-changeUserInfo
The following is an example of the iwtMailProvider-changeUserInfo attribute. This attribute specifies whether or not to update the user's IMAP server name, user id, and password information in the user info channel. If this attribute is set to true, the IMAP server name (see iwtMailProvider-IMAPServerName), user id (see iwtMailProvider-IMAPUserId), and password (see iwtMailProvider-IMAPPassword) specified via this component will overwrite the IMAP server name, user id, and password specified in the user info channel.
<iwt:Att name="iwtMailProvider-changeUserInfo"
desc="Change Mail Server attributes on UserInfo"
iwtMailProvider-IMAPServerName
The following is an example of the iwtMailProvider-IMAPServerName attribute. This attribute stores the user's IMAP server name.
<iwt:Att name="iwtMailProvider-IMAPServerName"
desc="IMAP ServerName to authenticate against"
The following is an example of the iwtMailProvider-IMAPUserId attribute. This attribute stores the user's IMAP server user id.
<iwt:Att name="iwtMailProvider-IMAPUserId"
The following is an example of the iwtMailProvider-IMAPPassword attribute. This attribute stores the user's IMAP server password.
<iwt:Att name="iwtMailProvider-IMAPPassword"
desc="Mail Server User Password"
iwtMailProvider-jspInboxNumLines
The following is an example of the iwtMailProvider-jspInboxNumLines attribute. This attribute specifies the number of lines from the Inbox to display on the corresponding client. This is only applicable to clients that utilize the mail JSP templates.
<iwt:Att name="iwtMailProvider-jspInboxNumLines"
desc="Number of Inbox Lines to Display Via JSP"
The following is an example of the iwtMailProvider-jspFromLength attribute. This attribute specifies the number of characters from the From header to display on the corresponding client. This is only applicable to clients that utilize the mail JSP templates.
<iwt:Att name="iwtMailProvider-jspFromLength"
desc="Length of From Header to Display Via JSP"
iwtMailProvider-jspSubjectLength
The following is an example of the iwtMailProvider-jspSubjectLength attribute. This attribute specifies the number of characters from the Subject header to display on the corresponding client. This is only applicable to clients that utilize the mail JSP template files.
<iwt:Att name="iwtMailProvider-jspSubjectLength"
desc="Length of Subject Header to Display Via JSP"
iwtMailProvider-jspMsgNumLines
The following is an example of the iwtMailProvider-jspMsgNumLines attribute. This attribute specifies the number of lines from the message to display on the corresponding client. This is only applicable to clients that utilize the mail JSP template files.
<iwt:Att name="iwtMailProvider-jspMsgNumLines"
desc="Number of Message Lines to Display Via JSP"
Address Book Provider Attributes
The attributes discussed in Table 8-5 reside in the profile component iwtAddressBookProvider.
iwtAddressBookProvider-clientURL
The following is an example of the iwtAddressBookProvider-clientURL attribute. This attribute's value can be specified from the administration console at the time of configuring the client channel.
The server URL used to build the Single Sign On link is configured in this profile attribute. This attribute uses a stringlist to store the clientType and the client specific server URL for that clientType. If the clientType is not found in the session, then the address book channel defaults it to generic HTML. The channel iterates through the list of values from this profile component attribute and gets the client URL based on the clientType accessing the address book server.
The isPresentable() method tries to get the client specific template for the channel content. If the template exists, then it returns true, else returns false.
<iwt:Att name="iwtAddressBookProvider-clientURL"
<Val>genericHTML|INST_AB_CLIENT_URL</Val>
iwtAddressBookProvider-displayEntries
The following is an example of the iwtAddressBookProvider-displayEntries attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the address book client
This attribute indicates whether or not to display the user's address book entries in the address book channel. By default, it is set to true.<iwt:Att name="iwtAddressBookProvider-displayEntries"
iwtAddressBookProvider-sortOrder
The following is an example of the iwtAddressBookProvider-sortOrder attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the address book client
This attribute indicates the order in which to sort the user's address book entries for display. The user can either select an ascending order or descending order of display of entries. By default, the address book entries are sort in an ascending order. The possible values are up and down.<iwt:Att name="iwtAddressBookProvider-sortOrder"
The following is an example of the iwtAddressBookProvider-sortBy attribute. This attribute gets its value:
From the administration console at the time of configuring the channel for the address book client
This attribute indicates the field in which to sort the user's address book entries for display. The user can either select to display entries by first name or last name. By default, the address book entries are sort by first name. The possible values are firstname and lastname.<iwt:Att name="iwtAddressBookProvider-sortBy"
iwtAddressBookProvider-numEntries
The following is an example of the iwtAddressBookProvider-numEntries attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the channel for the address book client
This attribute specifies the number of address book entries to display on the user's address book channel. By default, up to five entries will be displayed on the user's address book channel.Note that the number of entries that can be displayed is limited by the maximum number of entries allowed to be displayed on the channel (see iwtAddressBookProvider-maxEntries for more information).
<iwt:Att name="iwtAddressBookProvider-numEntries"
iwtAddressBookProvider-maxEntries
The following is an example of the iwtAddressBookProvider-maxEntries attribute. This attribute's value can be specified from the Administration Console at the time of configuring the channel for the address book client. This attribute indicates the maximum number of entries that can displayed on the address book channel. By default, up to thirty entries can be displayed on the user's address book channel.
<iwt:Att name="iwtAddressBookProvider-maxEntries"
desc="Maximum number of Entries"
iwtAddressBookProvider-LDAPServerName
The following is an example of the iwtAddressBookProvider-LDAPServerName attribute. This attribute's value can be specified from the Administration Console at the time of configuring the channel for the address book client. This attribute stores the address book database server name. This is used at the time of retrieving entries for the user and for performing searches in the address book database.
<iwt:Att name="iwtAddressBookProvider-LDAPServerName"
desc="Address Book LDAP server"
iwtAddressBookProvider-LDAPport
The following is an example of the iwtAddressBookProvider-LDAPport attribute. This attribute's value can be specified from the Administration Console at the time of configuring the channel for the address book client. This attribute stores the address book database server port number. This is used at the time of retrieving entries for the user and for performing searches in the address book database.
<iwt:Att name="iwtAddressBookProvider-LDAPport"
desc="Address Book LDAP server port"
iwtAddressBookProvider-LDAPAdminId
The following is an example of the iwtAddressBookProvider-LDAPAdminId attribute. This attribute's value can be specified from the Administration Console at the time of configuring the channel for the address book client. This attribute stores the address book database administrator's name. This is used at the time of retrieving entries for the user and for performing searches in the address book database.
<iwt:Att name="iwtAddressBookProvider-LDAPAdminId"
desc="Address Book Admin user DN"
iwtAddressBookProvider-LDAPAdminPassword
The following is an example of the iwtAddressBookProvider-LDAPAdminPassword attribute. This attribute's value can be specified from the Administration Console at the time of configuring the channel for the address book client. This attribute stores the address book database administrator's password. This is used at the time of retrieving entries for the user and for performing searches in the address book database.
<iwt:Att name="iwtAddressBookProvider-LDAPAdminPassword"
desc="Address Book Admin user password"
iwtAddressBookProvider-LDAPSearchBase
The following is an example of the iwtAddressBookProvider-LDAPSearchBase attribute. This attribute gets its value from the Administration Console at the time of configuring the channel for the address book client. This attribute specifies the directory search base in which to initiate the search for the LDAP directory.
<iwt:Att name="iwtAddressBookProvider-LDAPSearchBase"
desc="Searchbase for the LDAP directory"
iwtAddressBookProvider-IMAPServerName
The following is an example of the iwtAddressBookProvider-IMAPServerName attribute. This attribute's value can be specified from the Administration Console at the time of configuring the address book client channel. This attribute stores the user's IMAP server name. This is used for authentication of the Address Book users.
<iwt:Att name="iwtAddressBookProvider-IMAPServerName"
desc="IMAP ServerName to authenticate against"
iwtAddressBookProvider-IMAPUserId
The following is an example of the iwtAddressBookProvider-IMAPUserId attribute. This attribute gets its value from the edit Address Book page on the user's desktop. This attribute stores the user's IMAP user id. This is used to verify the validity of the credentials of the user against the specified IMAP server.
<iwt:Att name="iwtAddressBookProvider-IMAPUserId"
iwtAddressBookProvider-IMAPPassword
The following is an example of the iwtAddressBookProvider-IMAPPassword attribute. This attribute stores the user's IMAP user password. This is used to verify the validity of the credentials of the user against the specified IMAP server.
<iwt:Att name="iwtAddressBookProvider-IMAPPassword"
desc="Address Book User Password"
iwtAddressBookProvider-ldapConnPoolStart
The following is an example of the iwtAddressBookProvider-ldapConnPoolStart attribute. This attribute can be modified only by using the ipsadmin command (see "Configuring the Attributes"). This attribute specifies the number of LDAP connections to open initially in the connection pool used to connect to the LDAP server handling the address book. By default, upto five connections are established.
<iwt:Att name="iwtAddressBookProvider-ldapConnPoolStart"
desc="The number of LDAP connections to start off with"
iwtAddressBookProvider-ldapConnPoolMax
The following is an example of the iwtAddressBookProvider-ldapConnPoolMax attribute. This attribute can be modified only by using the ipsadmin command (see "Configuring the Attributes"). This attribute specifies the maximum number of LDAP connections to allow in the connection pool used to connect to the LDAP server handling the address book. By default, a maximum of twenty connections are allowed.
<iwt:Att name="iwtAddressBookProvider-ldapConnPoolMax"
desc="Maximum number of LDAP connections in the connection pool"
iwtAddressBookProvider-ldapOpTimeout
The following is an example of the iwtAddressBookProvider-ldapOpTimeout attribute. This attribute can be modified only by using the ipsadmin command (see "Configuring the Attributes"). This attribute specifies the amount of time, in milliseconds, after which the LDAP operation to the ldap server must terminate if it does not receive a response back from the server. By default, the LDAP operation will terminate after 20000 ms (20 seconds).
<iwt:Att name="iwtAddressBookProvider-ldapOpTimeout"
desc="The time in ms after which an ldap operation times out"
iwtAddressBookProvider-jspAbNumLines
The following is an example of the iwtAddressBookProvider-jspAbNumLines attribute. This attribute specifies the number of address book lines (entries) to display on the corresponding client. This is only applicable to clients that utilize the address book JSP template files.
<iwt:Att name="iwtAddressBookProvider-jspAbNumLines"
desc="Number of AB Lines to Display Via JSP"
The attributes discussed in Table 8-6 reside in the profile component iwtWirelessBookmarkProvider.
iwtWirelessBookmarkProviderWML-targets
The following is an example of the iwtWirelessBookmarkProviderWML-targets attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the client specific bookmark channel
This attribute stores the bookmarked URLs or resources for a WML client.<iwt:Att name="iwtWirelessBookmarkProviderWML-targets"
iwtWirelessBookmarkProvidercHTML-targets
The following is an example of the iwtWirelessBookmarkProvidercHTML-targets attribute. This attribute's value can be specified:
From the Administration Console at the time of configuring the client specific bookmark channel
This attribute stores the bookmarked URLs or resources for a cHTML client.<iwt:Att name="iwtWirelessBookmarkProvidercHTML-targets"
The attributes discussed in Table 8-7 reside in the profile component iwtXMLProvider.
The following is an example of the iwtXMLProvider-xslCache attribute. This attribute specifies whether or not caching of pre-processed XSLs to use for transformation is enabled. By default, this is enabled.
<iwt:Att name="iwtXMLProvider-xslCache"
<Rperm>ADMIN</Rperm><Rperm>OWNER</Rperm>
The following is an example of the iwtXMLProvider-url attribute. This attribute specifies the location of the XML content file or the URL that generates the XML content. This attribute can store:
URLs of type of HTTP or HTTPS
<iwt:Att name="iwtXMLProvider-url"
<Val>http://mum.red.iplanet.com:8080/books.xml</Val>
The following is an example of the iwtXMLProvider-xslFileName attribute. This attribute specifies the XSL template file to be used for transforming the XML content. It can store:
The absolute path to the XSL template file
See the Administration Guide for information on saving XSL template files.The base XSL filename. If this is specified, the path will be determined using the file lookup mechanism.
<iwt:Att name="iwtXMLProvider-xslFileName"
The attributes discussed in Table 8-7 reside in the profile component iwtJAXPJars.
Table 8-8    iwtJAXPJars Attributes
Attribute
Type
Description
Acceptable Value
This attribute stores the location of the JAXP (Java API for XML Parsing v1.1) jar files.
The following is an example of the iwtJAXPJars-jaxpJars attribute. This attribute stores the path to the JAXP jar files. This includes (and requires) the relative path from the directory where the iPlanet Portal Server server is installed (which is, by default, /opt). These files are used by the XML Provider for the XSLT engine and these files are used by all the XMLprovider channels.
<iwt:Att name="iwtJAXPJars-jaxpJars"
desc="Location of JAXP Jar Files relative to install dir."
<Val>SUNWips/lib/xmlp/crimson.jar</Val>
<Val>SUNWips/lib/xmlp/xalan.jar</Val>
<Val>SUNWips/lib/xmlp/jaxp.jar</Val>
Wireless URLScraper Provider Attributes
The attributes discussed in Table 8-9 reside in the profile component iwtWirelessURLScraperProvider.
iwtWirelessURLScraperProvider-url
The following is an example of the iwtWirelessURLScraperProvider-url attribute. This attribute stores the URL from which to scrape the contents for display on a HTML client. This default content URL is used for serving up content to HTML browsers. In order to serve this URL to other clients, add the list of clients to serve this URL to in the iwtWirelessURLScraperProvider-clientPresentableTo attribute.
<iwt:Att name="iwtWirelessURLScraperProvider-url"
<Val>http://www.iplanet.com</Val>
iwtWirelessURLScraperProvider-showAsLink
The following is an example of the iwtWirelessURLScraperProvider-showAsLink attribute. This attribute specifies whether or not to display the URL as a link on a mobile device instead of scraping and displaying the contents of the URL on the mobile device.
On a HTML or a cHTML client, the behaviour of the WirelessURLScraper is similar to the iPlanet Portal Server URLScraper. However, on a WML client, the WirelessURLScraper can display the contents of only the first card for WML pages, if the URL contains more than one card.
Since a mobile device has a small amount of memory and display area and since the scraped contents cannot have multiple cards, this attribute provides an option to display a link instead of scraping the contents in the URL.
<iwt:Att name="iwtWirelessURLScraperProvider-showAsLink"
desc="Display the URL as a link for non-desktop browsers"
The WirelessURLScraper uses the link.template file in the filePath attribute (defined for the clientType in iwtClient-clientTypes) under either:
<template_dir>/[channelName_as_provided_in_Wizard]/<clientType>
It uses the link.template file it first encounters.
<template_dir>/iwtWirelessURLScraperprovider/<clientType>
- Or
iwtWirelessURLScraperProvider-clientPresentableTo
The following is an example of the iwtWirelessURLScraperProvider-clientPresentableTo attribute. The default content URL is used for serving content to HTML browsers. If this URL can also be served to other HTML and non-HTML clients, add the clients in this attribute.This attribute stores the list of clients that can use the default content URL. If the value of this attribute is null (or if no client is listed in this attribute), all clients can use the default content URL. However, if this attribute contains some value (client), then only the listed clients can use the default content URL.
<iwt:Att name="iwtWirelessURLScraperProvider-clientPresentableTo"
desc="Clients that can use default URL"
iwtWirelessURLScraperProvider-urlList
The following is an example of the iwtWirelessURLScraperProvider-urlList attribute. The iwtWirelessURLScraperProvider-urlList attribute stores the default URLs for all of the supported clientTypes. When a client makes a request, the isPresentable() method looks-up the URL configured for the requesting clientType. If a URL is found, the scraper will return true, or false otherwise.
<iwt:Att name="iwtWirelessURLScraperProvider-urlList"
desc="List of URLs for various devices"
<Val>wml|http://wap.iplanet.com</Val>
<Val>wml|http://wap.sun.com</Val>
<Val>Nokia|http://wap.iplanet.com.nk</Val>
<Val>Nokia7110|http://wap.sun.com.nk7110</Val>
The URLScraper uses the iwtClient-clientTypes attribute in the profile to retrieve the URL most suitable for the client, based on the filePath for the particular client. For example, if the request comes from a Nokia 7110 phone, the scraper fetches the filePath from the iwtClient-clientTypes (such as filePath=wml/Nokia/Nokia7110) and looks in the iwtWirelessURLScraperProvider-urlList for the page most suitable for this device. It looks for Nokia7110, followed by Nokia, and falls back to WML in case no specific URL is available. Note that the search is case-sensitive.
Authentication Module Attributes
The attributes discussed in Table 8-10 reside in the profile component iwtAuth.
The following is an example of the iwtAuth-clientDetectionClass attribute. This attribute stores the name of the class implementing the client detection interface. By default, com.iplanet.portalserver.client.ClientDetector is the name of the client detection interface.
<iwt:Att name="iwtAuth-clientDetectionClass"
<Val>com.iplanet.portalserver.client.ClientDetector</Val>
iwtAuth-clientDetectionEnabled
The following is an example of the iwtAuth-clientDetectionEnabled attribute. This attribute indicates whether or not client detection is enabled for authentication. That is, this indicates whether or not to detect the clientType accessing the Mobile Access Pack server at the time of authenticating the client to the server.
The clientType is determined before any content is returned to the requesting client and the server looks up the contentType that the client accepts. Other components also use the clientType value as an index in the Client Data to retrieve information about the client accessing the server. By default, this is enabled.
<iwt:Att name="iwtAuth-clientDetectionEnabled"
desc="Client Detection Enabled"
To determine the client type, the ClientDetectionInterface will:
Determine the client type based on the request
Return a String representing the clientType
If there is an error retrieving the client data, throw a ClientDetectionException
The following is an example of the iwtAuth-supportedAuthModules attribute. This attribute stores the modules supported by a particular client as a string list with each value in the list having the clientType and the modules it supports. This is to enable the authentication service to identify which authentication modules are supported by a particular client. Based on the stringlist stored in this attribute, the authentication service displays only those module names which are supported by the requesting client in the authentication menu for the client.
<iwt:Att name="iwtAuth-supportedAuthModules"
desc="Supported Auth Modules for Clients"
<Val>default|Unix;Radius;Ldap</Val>
<Val>WML|Unix;Radius;Ldap</Val>
<Val>Nokia|Unix;SecureID</Val>
In the above example, the mobile client Nokia users are setup to use only UNIX and SecureID for authentication. Hence, when a user authenticates using a Nokia, the user is presented with an authentication menu that allows the user to log in using UNIX or SecureID.
By default, LDAP is the only supported authentication module for mobile devices.
Note The login worker class can be specific to a clientType and can serve content for different clientTypes. For example, if the clientType is WML, there can be a WmlLoginWorker class that can retrieve content specific to WML clients. See iwtAuth-loginWorkerClass and iwtAuth-loginWorkerClasses for more information.
The following is an example of the iwtAuth-LoginWorkerClass attribute. This attribute stores the loginWorkerClassName for HTML clients only. By default, com.iplanet.portalserver.auth.server.WirelessLoginWorker is the value for this attribute.
<iwt:Att name="iwtAuth-loginWorkerClass"
desc="Client Specific Auth Page Generator Classes"
<Val>default|com.iplanet.portalserver.auth.server.WirelessLoginWork er</Val>
The following is an example of the iwtAuth-loginWorkerClasses attribute. This attribute identifies which clientType must use which loginWorker class. This attribute is a stringlist storing the clientType and the loginWorker class name (clientType|loginWorkerClassName) for the specified client. By default, no values are defined in this attribute and the loginWorker class name is derived from iwtAuth-loginWorkerClass attribute.
<iwt:Att name="iwtAuth-loginWorkerClasses"
desc="Pluggable Auth page generator classes for clients"
<Val>genericHTML|com.iplanet.portalserver.auth.server.HTMLLoginWork er</Val>
<Val>WML|com.iplanet.portalserver.auth.server.WirelessLoginWorker</ Val>
<Val>cHTML|com.iplanet.portalserver.auth.server.WirelessLoginWorker </Val>
By default, this attribute uses the com.iplanet.portalserver.auth.server.WirelessLoginWorker class as the attribute value. The WirelessLoginWorker class also supports WML and cHTML clients.
Client Detection Module Attributes
The attributes discussed in Table 8-11 reside in the profile component iwtClient.
Table 8-11    iwtClient Attributes
Attribute
Type
Description
Acceptable Value
This attribute stores some critical client specific information for retrieving content specific to the client.
The following is an example of the iwtClient-defaultClientType attribute. This attribute stores the clientType that is supported by default. The default clientType supported by the Mobile Access Pack server is generic HTML.
<iwt:Att name="iwtClient-defaultClientType"
The following is an example of the iwtClient-clientTypes attribute.
<iwt:Att name="iwtClient-clientTypes"
<Val>clientType=genericHTML|userAgent=NeverWillMatchAUserAgent|cont entType=text/html|fileIdentifier=html|filePath=html|genericHTML=tru e</Val>
<Val>clientType=WML|userAgent=UP|contentType=text/vnd.wap.wml|fileI dentifier=wml|filePath=wml/UP|counterName=C|escapeWML=true|lineLeng th=20|charsets=ISO-8859-1;UTF-8</Val>
<Val>clientType=cHTML|userAgent=DoCo|contentType=text/html|fileIden tifier=chtml|filePath=chtml|escapeXML=true|lineLength=20|charsets=S hift_JIS</Val>
<Val>clientType=pana_p503i|contentType=text/html|fileIdentifier=cht ml|filePath=chtml/pana_p503i|genericHTML=false|userAgent=P503i|esca peXML=true|lineLength=20|charsets=Shift_JIS</Val>
<Val>clientType=siemens_s35|contentType=text/vnd.wap.wml|fileIdenti fier=wml|filePath=wml/UP|genericHTML=false|userAgent=SIE-S35|counte rName=C|escapeWML=true|lineLength=20|charsets=UTF-8;ISO-8859-1</Val >
<Val>clientType=nokia_7110|contentType=text/vnd.wap.wml|fileIdentif ier=wml|filePath=wml/Nokia/Nokia_7110|genericHTML=false|userAgent=N okia7110|counterName=C|escapeWML=true|lineLength=20|maxSize=2500|ch arsets=ISO-8859-1</Val>
This attribute is a string list with an embedded list of name=value pairs within each list element. Each list element contains one or more or the following information about the client:
charset - The charset element contains a supported (semicolon delimited list of) character sets for the corresponding client. The list specified here is displayed in the Edit Options page (on the user's desktop) for the corresponding client. This property's value must be specified when configuring the client.
clientType - The client type can be stored in this attribute as an arbitrary string (with a list of name=value pairs) uniquely identifying the client. This attribute serves as an index to the rest of the Client Data. By default, the following clients are supported:
clientType
Supported Clients
WML
Openwave browsers using WML
contentType - The contentType element contains the HTTP header value (such as text, html, wml). It specifies the acceptable content type for the requesting client. The contentType header is retrieved from the profile service and it can specified as a forward slash delimited list of acceptable content types. For fetching the contentType, the default clientType is used if client detection is disabled. This property's value must be specified when configuring the client.
counterName - This is used to add a counter to the URL.
escapeWML - This attribute is used by certain providers to handle content that contains special characters. This is a boolean attribute. If set to true, the special characters discussed below are escaped. The special characters that will be escaped within the provider content are:
Description
Symbol
Named Entity
Dollar
$
$$
Apostrophe
`
'
Quote
"
"
Ampersand
&
&
Less Than
<
<
Greater Than
>
>
escapeXML : This attribute is used by certain providers to handle content that contains special characters. This is a boolean attribute. If set to true, the special characters listed below are escaped. The special characters that will be escaped within the provider content are:
Description
Symbol
Named Entity
Quote
"
"
Ampersand
&
&
Less Than
<
<
Greater Than
>
>
fileIdentifier - The fileIdentifier element indicates the supported file types for the specified client.
filePath - The filePath element indicates the path to the client specific data files (such as templates and JSP files). Template and JSP files reside in sub-directories based on the desktop type, locale, and component (see "File Lookup Mechanism" for more information). For client specific file lookup, the search is based on the client's filePath attribute specified here. This property's value must be specified when configuring the client.
genericHTML - This attribute specifies whether or not the client accepts standard HTML.
ignoreHostHeader - This attribute makes the desktop ignore the host header. This is particularly useful when the host sends a HTTP/1.0 header.
lineLength -This specifies the number of characters that may appear on a single line of the device's display area.
maxSize - This is used to constrain the output size of the WirelessFrontProvider. It specifies the approximate number of bytes to send to the mobile device. The WirelessFrontProvider filters out the content restricting it to the maxSize limit specified here.
userAgent - The userAgent attribute stores a search string or filter. It is used to compare or match against the client's HTTP user agent header to determine the clientType. That is, the client detection module iterates over the supported list of clientTypes, comparing their userAgent against the user agent header of the client accessing the server. This property's value must be specified when configuring the client.
The attributes discussed in reside in the profile component iwtDesktop.
The following is an example of iwtDesktop-clientAllProviders attribute. This attribute stores a list of available channels for each supported client. This attribute is used to determine which channels are available to a given clientType.
<iwt:Att name="iwtDesktop-clientAllProviders"
desc="Client Specific Available Providers"
<Val>nokia_7110|iwtUserInfoProvider;iwtXMLProvider;iwtWirelessBookm arkProviderWML;iwtWirelessPersonalNoteProvider;iwtPostitProvider;iw tCalendarProvider;iwtMailProvider;iwtAddressBookProvider</Val>
<Val>siemens_s35|iwtUserInfoProvider;iwtXMLProvider;iwtWirelessBook markProviderWML;iwtWirelessPersonalNoteProvider;iwtPostitProvider;i wtCalendarProvider;iwtMailProvider;iwtAddressBookProvider</Val>
<Val>pana_p503i|iwtUserInfoProvider;iwtXMLProvider;iwtWirelessBookm arkProvidercHTML;iwtWirelessPersonalNoteProvider;iwtPostitProvider; iwtCalendarProvider;iwtMailProvider;iwtAddressBookProvider</Val>
<Val>WML|iwtUserInfoProvider;iwtXMLProvider;iwtWirelessBookmarkProv iderWML;iwtWirelessPersonalNoteProvider;iwtPostitProvider;iwtCalend arProvider;iwtMailProvider;iwtAddressBookProvider</Val>
<Val>cHTML|iwtUserInfoProvider;iwtXMLProvider;iwtWirelessBookmarkPr ovidercHTML;iwtWirelessPersonalNoteProvider;iwtPostitProvider;iwtCa lendarProvider;iwtMailProvider;iwtAddressBookProvider</Val>
iwtDesktop-clientUserSelectedProviders
The following is an example of the iwtDesktop-clientUserSelectedProviders attribute. This attribute stores a list of selected channels for each supported client. This attribute is used to determine which channels the user has selected to show up on a given client. If no channel is selected, the value of this attribute corresponding to the given clientType is removed from the profile.
<iwt:Att name="iwtDesktop-clientUserSelectedProviders"
desc="Client Specific Selected Providers"
<Val>nokia_7110|iwtUserInfoProvider</Val>
<Val>siemens_s35|iwtUserInfoProvider</Val>
<Val>pana_p503i|iwtUserInfoProvider</Val>
<Val>WML|iwtUserInfoProvider</Val>
<Val>cHTML|iwtUserInfoProvider</Val>
iwtDesktop-clientChannelListModules
The following is an example of the iwtDesktop-clientChannelListModules attribute. The iPlanet Portal Server channel list module provides a mechanism to store and retrieve multiple lists of selected and available channels.
The client channel list module extends the support for separate available and selected lists for each supported clientType. This allows users to specify what channels to display on their devices.
This attribute stores the client specific channel list modules to enable selection of channel by each user for each one of the devices setup for them.
<iwt:Att name="iwtDesktop-clientChannelListModules"
desc="Client Specific Channel List Modules"
<Val>nokia_7110|com.iplanet.portalserver.desktop.util.channellist.C lientChannelList</Val>
<Val>siemens_s35|com.iplanet.portalserver.desktop.util.channellist. ClientChannelList</Val>
<Val>pana_p503i|com.iplanet.portalserver.desktop.util.channellist.C lientChannelList</Val>
<Val>WML|com.iplanet.portalserver.desktop.util.channellist.ClientCh annelList</Val>
<Val>cHTML|com.iplanet.portalserver.desktop.util.channellist.Client ChannelList</Val>
Previous Contents Index Next
Copyright © 2001 Sun Microsystems, Inc. All rights reserved.
Last Updated November 14, 2001