Downloads  |  Product Documentation  |  Support

dev2dev Home      Developer Centers      CodeShare      Community      Newsgroups     

eDocs Home > BEA WebLogic Portal 10.0 > Use with Multibyte Environments

Using BEA Weblogic Portal 10.0 in Multibyte Environment

This document contains the following:

• Localizing Popup Text and Messages of Portlet Icons
• Creating Non-UTF-8 Encoding-Based Portal Applications
• Adding Fonts to Rich Text Editor in GroupSpace
• Multibyte Character Search Using GroupSpace Enterprise Search
• Editing Community Email Invitations
• Setting of maximum value for file descriptor at the time of portal domain startup
• Known Limitations on BEA WebLogic Portal 10.0 in Multibyte Environment

See BEA Product Documentation for the latest information.

Localizing Popup Text and Messages of Portlet Icons

The netuix-config.xml file contains the popup text for portlet icons. You can add a localized text (in boldface) as shown below. The following example shows localization to Japanese by adding the locale ja.

   <!-- Container supported widow states -->
   <window-state name="minimized">
        <activate-image>titlebar-button-minimize.gif</activate-image>
        <deactivate-image>titlebar-button-unminimize.gif</deactivate-image>
        <alt-text>
            <locale language="ja">
                <activate>最小化</activate>
                <deactivate>元に戻す</deactivate>
            </locale>
            <locale language="en">
                <activate>Minimize</activate>
                <deactivate>Restore</deactivate>
            </locale>
        </alt-text>
    </window-state>

The netuix-config.xml file will be created in the WEB-INF directory after a portal Web project is created in Workshop.

Creating Non-UTF-8 Encoding-Based Portal Applications

This section gives an example of creating a Shift_JIS-based Japanese portal application. When creating a Shift_JIS-based JSP or PageFlow in portal applications, you have to configure the JSP or PageFlow as well as the portal itself.

The following is the first step to create a JSP or PageFlow with Shift_JIS encoding.

1. Edit or add JSP ContentType.

   
       <%@ page language="java" contentType="text/html;charset=Shift_JIS"%>
   

 

2. Edit or add weblogic.xml charset-params.
   
   Add the following statements after <wls:context-root/> but before <wls:library-ref>.

   
       <wls:charset-params>
   
         <wls:input-charset>
   
           <wls:resource-path>/*</wls:resource-path>
   
           <wls:java-charset-name>Shift_JIS</wls:java-charset-name>
   
         </wls:input-charset>
   
       </wls:charset-params>
   

    

   Then, set the portal as follows:
3. Edit netuix-config.xml.
   
   Add the following statement before </weblogic-portal-app>.

   
       <default-encoding encoding="Shift_JIS" />
   

 

4. Edit the portal file.
   
   The .portal file has the encoding setting in the netuix:desktop tag. The default is UTF-8. For Shift_JIS-based applications, this setting must be changed as shown below.
   
   The source can be edited when the .portal file is opened by explicitly specifying the XML editor on the Workshop menu.

   
       <netuix:desktop  encoding="Shift_JIS"/>
   

Adding Fonts to Rich Text Editor in GroupSpace

When settings are enabled in web.xml, the rich text editor screen is displayed for several portlets of GroupSpace.Fonts can be selected in this editor. By default, only particular English fonts are on the list. You can type and view multibyte characters with those fonts. However, use the following procedure if you want to add a font to the list.

1. Expand <WL_HOME> /portal/lib/modules/wlp-commonui-web-lib.war.
2. Edit wlp/pinEdit/editor/config/config_toolbar_auto_custom.js using the editor.
3. Locate the case "20": // Font line in the source.
4. Add the following statement with the desired font name under the // add item line in the case statement.

   
       cmbFont.add(objToolbars.createStyleComboItem("<FONT unselectable='ON' face='font name'>font name</font>","","","font name"));
   

 

5. Save the file. Be sure to save it in the UTF-8 format.
6. Reflect the edited file to <WL_HOME>/portal/lib/modules/wlp-commonui-web-lib.war.

Note: When the application is new to the domain, use this procedure before deploying the application. When an existing domain is updated, the application must be redeployed.

Multibyte Character Search Using GroupSpace Enterprise Search

Using the GS Enterprise Search portlet in GroupSpace, you can search contents of files under the specified directory, the page at the specified URL, or the linked page.

To search files or pages containing Japanese or other multibyte characters, the following settings are required.

1. Edit <WL_HOME>/cm/thirdparty/autonomy-wlp10/<PLATFORM_TYPE>/IDOLserver/IDOL/AutonomyIDOLServer.cfg.
   
   In the [Server] section, set AutoDetectLanguagesAtIndex to FALSE (Default value), and in the [Language Types] section, specify the encoding for the files or pages to be searched.More than one encoding cannot be handled at the same time.
   
   Example: When specifying Japanese UTF-8

   
   [Server]
   AutoDetectLanguagesAtIndex=FALSE
   ....
   [LanguageTypes]
   DefaultLanguageType=japaneseUTF8
   DefaultEncoding=UTF8
   

2. To search the contents of Word, Excel, Powerpoint or PDF files, the following setting is also required.
   
   <WL_HOME>/cm/thirdparty/autonomy-wlp10/<PLATFORM_TYPE>/filters /omnislave.cfg

   
   [MSWord]
   OutputCharSet=UTF8
   ....
   [Xls]
   OutputCharSet=UTF8
   ....
   [Ppt]
   OutputCharSet=UTF8
   

   <WL_HOME>/cm/thirdparty/autonomy-wlp10/<PLATFORM_TYPE>/filters /pdfslave.cfg

   
   [Configuration]
   OutputUTF8=TRUE
   

3. Edit web.xml of the portal Web project.

Add the context-param element and specify the encoding for the files or pages to be searched.

Example: When specifying UTF-8

<context-param>
  <param-name>com.bea.apps.groupspace.search.enterprise.outputEncoding</param-name>
  <param-value>UTF8</param-value>
</context-param>
<context-param>
  <param-name>com.bea.apps.groupspace.search.enterprise.connectionEncoding</param-name>
  <param-value>utf-8</param-value>
</context-param>

Note: Specify the IDOLEncodings name for outputEncoding, and the lower-case IANA encoding name for connectionEncoding.

Editing Community Email Invitations

You can edit community email invitations using the following procedure.

1. Open the portal Web application using Workshop.
   
   Note: To use this function, you have to select the "WebLogic Portal Collaboration" option when creating the portal Web application.
2. Open the "Merged Projects" tab.
3. Expand "invitations/email" in the project tree.
4. Right-click the following files and select "Copy To Project".
   • invite_body.jsp
   • invite_subject.jsp
5. Open the "Navigator" tab.
6. Expand the project tree and edit the copied files as follows:
   
   Example of modifying invite_subject.jsp

   
   <%@ page contentType="text/plain;charset=UTF-8" %>
   
   <%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
   
   <c:choose>
   
   <c:when test="${empty pageFlow.customMessageFromName}">
   
    You have been invited to community ${pageFlow.communityTitle}!
   
   </c:when>
   
   <c:otherwise>${pageFlow.customMessageFromName} is inviting you to GroupSpace 
   
   "${pageFlow.communityTitle}!".
   
   </c:otherwise>
   
   </c:choose>
   

    

   Example of editing invite_body.jsp

   
   <%@ page contentType="text/plain;charset=UTF-8" %><%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
   
   The ${pageFlow.communityTitle} GropSpace is inviting you.
   
   <c:if test="${!empty pageFlow.customMessageBody}">
   <c:choose><c:when test="${empty pageFlow.customMessageFromName}">
   
   Message from the member inviting you:
   
   </c:when><c:otherwise>
   
   Message for you from ${pageFlow.customMessageFromName}.
   
   :</c:otherwise></c:choose>
   
   "${pageFlow.customMessageBody}"
   
   </c:if>
   
   You can manage the following items from the ${pageFlow.communityTitle} GroupSpace.
   
   
     * Discussion forums
   
     * Public/personal links to related project information
   
     * View integrated email with your enterprise collaboration services
   
     * Manage RSS news feeds
   
     * Share and manage content-rich documents
   
   
   URL:
   
   ${pageFlow.registrationURL}
   
   
   You will be welcomed!
   

Setting of maximum value for file descriptor at the time of portal domain startup

When portal domain is started by using Localized Installer, an exception called "Too many open files" may occur in case of server start.This exception shows the problems generated in the resource of operating system, as file descriptors are not sufficient in the operating system and JVM process.Refer to Too many open files of trouble-shooting guide support diagnosis pattern and change the number of definitions of file descriptors as needed.

Known Limitations on BEA WebLogic Portal 10.0 in Multibyte Environment

The following table shows supplementary information about multibyte environment for Known Limitations and Workarounds in BEA WebLogic Portal 10.0.