Install the Authoring portlet

 

+
Search Tips   |   Advanced Search

 

The Authoring portlet configuration task will automatically create IWWCM pages and install the Authoring portlet and Local Rendering portlets.

 

Run the configuration task:

  1. Verify SOAP settings are correct...

    • soap.client.props file - timeout value is 6000.
    • wpsadmin.properties file - SOAP port is defined correctly.
    • wasadmin is able to connect to the server1 natively without error.

  2. Add the WebSphere Portal administrators group to the wcmadmins group in WebSphere Portal administration:

  3. Open a command prompt.

  4. Run the configure-wcm-authoring task:

    Error executing task...

  5. Log out of the portal and log back in.

    If you are running in a cluster, cycle the portal application server.

  6. Select Web Content from the main menu to access the Authoring portlet.

  7. Apply WCM fixes

 

Locale consistency

The language displayed in the WCM Authoring portlet is determined by the region or locale of the user. There are, however, some elements of the Authoring portlet that use WebSphere Portal functions, such as date selection fields. These will be displayed using the locale of the WebSphere Portal server. For this reason, the language and locales of the site being created, the client and server should be consistent.

If the site contains content in different languages, then separate WCM authoring applications should be setup for each language on different WebSphere Portal Servers. These can then be combined into one site using a staging server.

If a user changes their locale, any currently opened WCM dialogs will be closed. A user will also have to start a new session before it is displayed using the new locale. It is best practice to have the client's correct locale set prior to using WCM.

 

"EJPXB0015E"

$ ./WPSconfig.bat configure-wcm-authoring -DPortalAdminPwd=password

...

ADMA5058I: Application and module versions validated with versions of 
       deployment targets.

ADMA5005I: The application WCM_Authoring_UI_PA_f0su8tb is configured in the 
       WebSphere Application Server repository.

ADMA5053I: The library references for the installed optional package are created.

ADMA5005I: The application WCM_Authoring_UI_PA_f0su8tb is configured in the 
       WebSphere Application Server repository.

ADMA5001I: The application binaries are saved in...

C:\ibm\WebSphere\profiles\wp_profile\wstemp\wp_10d40fdf747\workspace    \cells\skycell1\applications\WCM_Authoring_UI_PA_f0su8tb.ear    \WCM_Authoring_UI_PA_f0su8tb.ear 
[xmlaccess] EJPXB0015E: Server response indicates an error.
[xmlaccess] EJPXB0015E: Server response indicates an error.

BUILD FAILED
file:../config/includes/wcm_cfg.xml:671: EJPXB0015E: Server response indicates an error.

Total time: 20 minutes 6 seconds

Line 671 of the wcm_cfg.xml file contains 

<target name="configure-wcm-authoring"
    depends="init" 
    unless="isSecondNode">

  <logmsg level="INFO"
      task="configure-wcm-authoring"
      message="Config.general"
      param1="configure-wcm-authoring"/>

  <antcall target="start-portal-server"/>

  <xmlaccess user="${PortalAdminIdShort}"
         password="${PortalAdminPwd}"
         srcfile="${WpsInstallLocation}/wcm/deploy/DeployWcmAuthoringPortletAndPage.xml"/>


  <antcall target="action-http-wcm-search-collection"/>

  <antcall target="action-set-wcm-authoring-configured">

    <param name="WcmAuthoringConfiguredParam" value="true"/>

  </antcall>

I'm going to try passing PortalAdminIdShort as a parameter to the command...

./WPSconfig.bat configure-wcm-authoring -DPortalAdminIdShort=wpsadmin -DPortalAdminPwd=password

...that fixed problem...

 

EJPXA0043E

[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10038/wps/config/
[xmlaccess] EJPXB0002I: Reading input file         C:\IBM\PORTAL~1\wcm\deploy\DeployWcmAuthoringPortletAndPage.xml 
<!-- 1 [skin ibmSkin uniquename=ibm.portal.skin.IBM] -->
<!-- 2 [skin noSkin uniquename=wps.skin.noSkin] -->
<!-- 3 [skin ThinSkin uniquename=wps.skin.thinSkin] -->
<!-- 4 [web-app uid=BlurbPortlet.3088d83ae7690017105c9e64cce97eb8] -->
<!-- 5 [portlet-app uid=BlurbPortlet.3088d83ae7690017105c9e64cce97eb8.1] -->
<!-- 6 [portlet information.portlet uniquename=wps.p.Information name=Information Portlet] -->
<!-- 7 [web-app wcm.author.1001 uid=wcm.author.1001] -->

<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     build="wp600_244"
     type="update"
     version="6.0.0.0" xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd">

  <status element="[web-app wcm.author.1001 uid=wcm.author.1001]"
         result="failed">
         <message id="EJPXA0043E">
               com.ibm.wps.command.xml.XmlCommandException:
               EJPXA0043E: An error occurred while creating or updating the                resource. [web-app wcm.author.1001 uid=wcm.author.1001]</message>

    <message id="EJPPD0015E">
          com.ibm.wps.command.CommandFailedException:
          EJPPD0015E: Portlet application manager failed when user xmlaccess
          scripting user executed command InstallWebApplication.</message>

    <message id="EJPPH0019E">
          com.ibm.wps.pe.mgr.exceptions.AppServerWarInstallException:
          EJPPH0019E: Installation of Web module wcm.author.1001 from WAR file
          C:\IBM\PORTAL~1\deployed\ilwwcm-authoring-portlet.war failed           (
          display name: WCM_Authoring_UI_PA_f0v1w28,
          options: AppServerDeploymentData 
          id           = wcm.author.1001
          displayName  = WCM_Authoring_UI_PA_f0v1w28
          warfileName  = C:\IBM\PORTAL~1\deployed\ilwwcm-authoring-portlet.war           contextRoot  = /wps/PA_f0v1w28
          fileLoader   = DirectoryFileLoader(C:\IBM\PORTAL~1\deployed\temp\ilwwcm-authoring-portlet.war.1)
          ).</message>

    <message id="EJPPH0040E">
          com.ibm.wps.pe.mgr.exceptions.AppServerAdminConfigSaveException:
          EJPPH0040E: Failed to save configuration changes to Application Server.</message>

    <message>
          com.ibm.websphere.management.exception.ConfigServiceException:
          com.ibm.websphere.management.exception.ConnectorException:
          ADMC0009E: The system failed to make the SOAP RPC call: invoke</message>
  </status>
</request>

[xmlaccess] EJPXB0015E: Server response indicates an error.
[xmlaccess] EJPXB0015E: Server response indicates an error.

BUILD FAILED
file:../config/includes/wcm_cfg.xml:677: EJPXB0015E: Server response indicates an error.
Total time: 37 minutes 4 seconds

To fix, make wpsadmins group a member of wcmadmins group and verify SOAP settings...

  • soap.client.props file - timeout value is 6000.
  • wsadmin.properties file - SOAP port is defined correctly.
  • wsadmin is able to connect to the server1 natively without error.

 

Parent topic:

Configuring an authoring server