There is a new beta release available today! Below are details about this release and this append will be updated and/or responded to as more information becomes available. Please review the information below for details on the updated release.
You can expect more frequent beta release updates between now and V6.1 becoming generally available. The WebSphere development team looks forward to your feedback and thanks for all of the comments to date.
Happy New Year to beta participants!
General comments:
The latest beta release (currently only available for Windows and Linux) is now built upon WebSphere Application Server V6.1.
Please use this forum to report problems and request support.
Please install this beta release on a machine that does not have an existing WebSphere Portal Server or DB2 version installed.
Enabling LDAP is not supported in this beta release.
This version is available as English only. It is suggested that you set the language preferences to English (United States) en-US in "Edit My Profile".
This version installs DB2 v9.1, however, you will need to manually transfer to DB2 if you wish to use DB2 (this limitation will be removed by the next beta release). Other database support is not currently available.
It is recommended to install to a short folder path name, like: C:\ibm\pe rather than the default install path.
You are required to install with the default user id and password (xyzadmin/xyzadminpw). If xyzadminpw does not meet the password requirements of the install machine, please alter your password requirements or wait for the next beta release.
In general, Firefox supports more features than Internet Explorer in this beta release.
Known limitations with the current beta release:
Cannot save a new theme edited with the Theme Customizer
Post a link command from About page within Internet site does not work
Content library name still references 6.0.2
@nls@... may be seen in some content portlets
Issues with editing content portlets (on Intranet and Internet sample sites)
People picker is not working properly
Policy is not supported
Site Management publish feature is not available
Drag/drop from portlet palette has some limitations
Previous limitations for your review (need to log into developer works for this link)
If you wish to perform a database transfer, complete the following steps:
edit the ConfigEngine/properties/wkplc_comp.properties
update each domain property to the new DbType
for example, release.DbUser, community.DbUser, customization.DbUser, jcr.DbUser, feedback.DbUser, likeminds.DbUser, etc
edit the ConfigEngine/properties/wkplc_dbtype.properties
edit the section just as you would in wp6.0.x and update it for the new dbtype files
Hi Travis; what about the short CELL name requirement? For example to get my installation to succeed on Windows I had to shorten the cell name to PCELL01. I didn't have a problem using a long path name. I used:
Hi - I would suggest continuing to use a short cell name as well.
Thanks,
--travis
PS - For anyone trying to transfer to DB2, some folks have had success and others not. You may wish to wait 2-3 weeks - we should have a refresh that installs directly to DB2 like the initial beta release.
Hi Travis, I noticed that I now have to use ConfigEngine.sh instead of WPSconfig.sh for configuration task. Am I right when I say that 6.1 will move away WPSconfig? Also because I'm coming late to Portal 6.1 Beta testing, is this forum mainly for reporting problems with the Beta code? Or can we also ask questions about configuration changes, new ways of doing things, etc.
Yes, Portal 6.1 will use ConfigEngine.sh and WPSconfig.sh will no longer be available.
Many of the same configuration task will be available though. This change is part of an overall change to separate the writable files in portal (configuration properties files etc.) from the read-only files (Java .jar files etc.)
I'm not sure I totally understand the question.
Portal used a WAS profile in 6.0.x as well. New for 6.1 is a consolidation of writable files in the profiles area.
The default path on Linux is something like /opt/IBM/PE/AppServer/profiles/wp_profile.
On windows the default path is something like C:\IBM\WebSphere\wp_profile
Where is the download located? Clicking on the link takes me to the beta page, which still links to the 'beta1' download from July. Thanks
Sorry about that, in our haste to post a new drop before end of year, we neglected to update the comments. If you follow the same links, you will find new code.
Updates to the download site will be arriving shortly. (PS - you are not required to download the W-6 or IL-6 file).
Quick feedback from an initial evaluation of this beta drop. This is clearly a work in progress, but the direction of the (Express) user interface is encouraging. It's getting closer and closer to "purpose" built, which is an essential attribute to be competitive in the mid-market. Keep up the good work - and the usability testing!
