1. Install Phyton

Follow these steps wget http://www.python.org/ftp/python/2.5.5/Python-2.5.5.tgz tar -xvzf Python-2.5.5.tgz cd Python-2.5.5 ./configure –prefix=/usr/local/python2.5 make make test sudo make install sudo ln -s /usr/local/python2.5/bin/python /usr/bin/python2.5

2. Install Scons

Visit the www.scons.org website and select the “Tarball”, because we are going to build the scons manually

3. Download the Appcelerator source code from GitHub

4. Make sure that you extract the sourcecode files into the folder which contains NO space, otherwise it will not be able to compile later on

5. Set the JAVA_HOME

Type: JAVA_HOME= Type: export JAVA_HOME

6. Set the PATH

Type: PATH=$JAVA_HOME/bin:$PATH Type: export PATH

7. In Linux, you can only build android codes, so you need to add the Android SDK into your scons parameter as follow

scons android_sdk=

for example: scons android_sdk=/apps/android/androidSDK11/android-sdk-linux_x86/

8. Compiling and make sure that you see the BUILD SUCCESSFUL

Google API

Possible Errors: 1. package com.google.android.maps does not exist

Make sure that you have installed the Google API in the Android SDK. How to do this? Use the Android SDK and AVD Manager to install Google API from the Available Packages, then select Google Inc, and select the latest Google API.

Google API

You might need to add the maps.jar into the ANT build classpath. Edit the common.xml, and Find the path id=”android”, to add the maps.jar

Google API

These are the steps:

1. If you do not have iTunes, make sure that you download the latest iTunes. This program is used to upgrade, downgrade, and restore the iPhone OS.
2. Install this iTunes and make sure that you are able to do the SYNCH between your PC (Mac or Windows) with your iPhone
3. Since there is no proven JailBreaker that is able to completely jailbreak iPhone 3.1.3, so what I did was to downgrade to 3.1.2. You can download from anywhere, for example: Redmond. Make sure that you download the iPhone OS Firmware 3.1.2
4. Before you downgrade to 3.1.2, make sure that you backup all your iPhone data to your iTunes on you PC
5. Click CTRL + Restore on the iTunes.  It will ask you the location of the OS 3.1.2 .psw file.
6. Select that file, and then let it start the restoration, I mean downgrading.
7. In the meantime, you can download the blackrain. This is the core program to enable you to jailbreak your iPhone, in other words, to enable your iPhone to install applications (games, themes, ringtones, or other widgets) from other repositories, not the default iTunes AppsStore.
8. I believe, you will not be able to complete the restoration, as the iTunes will throw the error: 1005. DO NOT worry about it. That’s normal.
9. Now, click the BlackRain executable and let it start the ‘rain’.
10. Let it finish the whole set of tasks, and at the end, your iPhone is now already in 3.1.2 OS.
11. Now, click the BlackRain again, to do the actual Jailbreaking.
12. WOW, I believe now you should be able to see this image on your iPhone upon rebooting
13. 
14. Then, DONE

Now, start the downloading

1. Click the blackra1n icon on your iPhone
2. Let it start installing the installers.
3. You can start with  Cydia and Rock. These are just repositories utilities  which allow you to browse through the free apps and commercial apps

Now, enjoy your new JAILBROKEN iPhone.

The first thing you need to understand is the Places Services REST API.

The Quickr REST Places services are accessible through this URL: <hostURL>/myqcs/rest/places/feed, i.e. http://localhost:10038/myqcs/rest/places/feed

Once you hit that URL, if you provide the correct username and password, you will see this

If you view the sources, you will see this

Scroll to the very bottom…

For each of the Place entry, there are other REST URLs for the entry, roles, and members, even the document libraries.

Now, we look at the entry feed

You see bunch of place parameters which you can change, using the POST REST call

For our case, we will focus on the roles entry

Now, open the roles URL, then you will see this

Depends on which Role you want to edit the members, the URL will be different.  For example, let’s say we want to add member for the “Contributor” role, then we should use the “related” URL of the “Contributor” role (see below)

Take note on this URL, since we are going to use this one in our code

Now, how does Quickr handle this REST Call?

Basically Quickr 8.1.1 handles the REST Call through the “rest.placeservices” Enterprise Application

The code is all there, so in the next section, we will change some of the codes (extend the Java Classes) to meet our requirement

This EAR is basically a Web Application, supported by Struts and Abdera framework  (see below)

This is the Struts.xml file content

The above shows the section of the struts-config.xml of this Web application.

Well, just take note on those action mappings, as we just need to extend those action mappings

So, where is the modification?

The above section mentions to change the action mappings. Well, this is the struts mapping after changes

Notice on the “/places/feed” and “/places/*/roles/*/members”. The first one is NOT used in this use case, but the second one is.

The files above contain the new Java classes used for this modification

This is the change of the “NTUCStrutsPlaceMembersForRole”

Force it to call the “NTUCPlaceServiceImpl” instead of the “PlaceServiceImpl” class

This is the “addMemberToApplication” function implementation.

…

…

Take note on this section

It splits the memberInfo by ‘|’, that means that now the REST API client must follow this pattern: <memberDN>|<memberType>

Okay fine.., so how do we deploy this code then?

Two things to deploy, first one is the “struts-config.xml” file

Just replace it to the location as shown above

Secondly is the classes files, just deploy to the location as shown below

So, how are we testing it?

We create one simple Java Program (“TestAddMember.java”)

After added, then we see the result

You can try this link, to set the WebSphere Variable

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.express.doc/info/exp/ae/trun_svr_timezones.html

Another option is to modify the WebSphere Application Server command line arguments to use a specific timezone. Please do the following steps:

1. Go to: Application servers > WebSphere_Portal > Process Definition > Java Virtual Machine

2. In Generic JVM agrument box. Add the following at the end of the command

-Duser.timezone=<id>

Example:
-Duser.timezone=Asia/Singapore

3. Stop and restart the portal server.

To me, it looks like this is IE 8 bug:

http://connect.microsoft.com/IE/feedback/details/381508/webpage-has-expired

So, when you encounter the similar problem, just leave it, or you can change the method from GET to POST.

It’s been a very long time not to post anything into my blog. It’s been very busy lately. Well, now let me start off by posting new technology on how to use EPHOX and customize it to replace the IBM WCM Rich Text Editor (RTE)

1. Go to this folder
/usr/IBM/WebSphere/wps/wp_profile/installedApps/cxwps02/PA_WCM_Authoring_UI.ear/ilwwcm-authoring.war/res/editlivejava
Create a copy of the “sample_eljconfig.xml” file, let’s say eljconfig.xml.
Change the “toolbarComboBox” item

2. And remove the unnecessary font types or sizes and refresh the browser
Change the /usr/IBM/WebSphere/wps/wp_profile/installedApps/cxwps02/PA_WCM_Authoring_UI.ear/ilwwcm-authoring.war/jsp/html/EditLiveJavaEditor.jsp

3.  Now testing

Well, if you want to install, follow these steps:

1 Before You Begin

1.1 Backups
Always backup your portlets before performing any of the installation procedures outlined in this document.

1.2 Recommended ILWCM Fix Level
Upgrading to ILWCM 6.1.0.1 Cumulative Fix 6 or later is recommended prior to installing the editor.

1.3 Upgrade Process for Cumulative Fixes and Fixpacks
The appropriate instructions for “Re-deployment after an upgrade” for Single Server Deployment or Clustered Deployment must be followed after every ILWCM cumulative fix install and every Websphere Portal fixpack install.

1.4 First-time Installation
If you do not have the updated rich text editor already installed on your ILWCM deployment, you must follow the appropriate “Initial Installation” instructions for either a Single Server Deployment or Clustered Deployment.
Also you must use the editor package downloaded from Passport Advantage or received on CD. This will ensure all of the appropriate files are deployed, including the necessary license key.

1.5 Ensuring Latest Editor Version
When installing the editor for the first time, please note there may be a later fix of the editor available for download. Please download the latest fix level from Fix Central, then:
· First follow the “Initial Installation” instructions with the editor package you downloaded from Passport Advantage or received on CD
· Then follow the “Applying an Editor Fix” instructions with the editor fix you
downloaded from Fix Central If you have already installed the editor, you can check Fix Central for editor fixes, or you may be instructed to install an editor fix by IBM support. After downloading or receiving a fix, follow the “Applying an Editor Fix” instructions.

2 Single Server Deployment

2.1 Initial Installation
These instructions are to be used when deploying the updated editor onto your ILWCM deployment for the first time in a single server environment.
Step 1 – Copy Integration Files to Portal Server Machine
Copy the editor files to a temporary location on the machine hosting the IBM
Websphere Portal Server.
Step 2 – Copy Integration Files to ILWCM Root Directory
1. Copy the contents of the web directory, located at the temporary directory
where the editor files were placed.
2. Paste these files into the root directory of your installed ILWCM Authoring
Portlet Example: For Websphere 6.1: The root directory for your ILWCM Authoring
Portlet will be similar to the following:
C:/Program Files/IBM/Websphere/wp_profile/installedApps/
[nodeName]/PA_WCM_Authoring_UI.ear/ilwwcmauthoring.
war
3. In order to use the editor to edit content inline, you’ll also need to paste these files into the root directory of your installed ILWCM Local Rendering Portlet Example: For Websphere 6.1: The root directory for your ILWCM Local Rendering Portlet will be similar to the following:
C:/Program Files/IBM/Websphere/wp_profile/installedApps/
[nodeName]/PA_WCMLocalRendering.ear/ilwwcmlocalrende.
war
Step 3 – Specify the editor as the default in ILWCM
1. Log in to Websphere Portal as a user with administrative access
2. Configure the ILWCM Authoring Portlet to use the editor
a. Navigate to the ILWCM Authoring Portlet
b. Click on the Configure link
c. Expand the Rich Text Options section
d. In the text field that displays, enter EditLiveJavaEditor.jsp
e. Click OK
3. If you also wish to use the editor to edit content inline:
a. Navigate to the Administration section, then Portlet Management, Portlets
b. Search for the “Web Content Viewer” portlet
c. Click the Configure Portlet button next to the “Web Content Viewer” portlet
d. Enter a new parameter “WCM_RICH_TEXT_EDITOR” with the new value of “/jsp/html/EditLiveJavaEditor.jsp”
e. Click Add to add the new parameter
f. Click OK to save the configuration change

2.2 Re-Deploying Editor After an Upgrade
These instructions are to be used when re-deploying the updated editor after upgrading your ILWCM deployment in a single server environment.
NOTE: this procedure must be followed after both cumulative fix and fixpack installs.
Step 1 – Backup Integration Files
Backup these files and one directory (including all contents of this directory)
from the root directory of your ILWCM Authoring Portlet:
/jsp/html/customFunctionality.jsp
/jsp/html/EditLiveJavaEditor.jsp
/jsp/html/sharedMethods.jsp
/res/editlivebaseurl.js
/res/EditLiveJavaEditor.js
/res/editlivejava
Step 2 – Install ILWCM Upgrade
Perform ILWCM upgrade as per instructions.
Step 3 – Restore Integration Files
1. Restore the files and directories backed-up in step 1. into the root directory of your installed ILWCM Authoring Portlet
2. If the editor is being used to edit content inline then you must also restore the backed-up files into the root directory of your installed ILWCM Local
Rendering Portlet

2.3 Applying an Editor Fix
These instructions are to be used when applying a fix to the updated editor on an ILWCM deployment in a single server environment.
Step 1 – Copy Integration Files to Portal Server Machine
Move the editor files to a temporary location on the machine hosting the IBM
Websphere Portal Server.
Step 2 – Copy Integration Files to ILWCM Root Directory
1. Copy the contents of the web directory, located at the temporary directory
where the editor files were placed.
2. Paste these files into the root directory of your installed ILWCM Authoring
Portlet
Example: For Websphere 6.1: The root directory for your ILWCM Authoring
Portlet will be similar to the following:
C:/Program Files/IBM/Websphere/wp_profile/installedApps/
[nodeName]/PA_WCM_Authoring_UI.ear/ilwwcmauthoring.
war
3. If the editor is being used to edit content inline, you’ll also need to paste these files into the root directory of your installed ILWCM Local Rendering Portlet
Example: For Websphere 6.1: The root directory for your ILWCM Local
Rendering Portlet will be similar to the following:
C:/Program Files/IBM/Websphere/wp_profile/installedApps/
[nodeName]/PA_WCMLocalRendering.ear/ilwwcmlocalrende.
war

After months of troubleshooting in our client side, we finallymanaged to solve the Multi /GET/Command.Login issue in our WebSphere Portal environment.

Basically it is caused by the unproper JSESSIONID cookie handling by the WPS 6.0. These are the steps to solve it:

1. Change the WebSphere Portal cookie name to something else, as long as not JSESSIONID (let’s say FERNANDO-JSESSIONID)
2. Navigate to Resources->Resource Environment providers->WP PortletServiceRegistryService->Custom Properties
3. Add the following custom properties: com.ibm.wps.pb.service.PropertyBrokerServiceImpl.sessionid.cookie.names =<new_cookie_name> and com.ibm.wps.propertybroker.standard.service.PropertyBrokerServiceWrapper.com.ibm.portal.propertybroker.standard.sessionid.cookie.names.property = <new_cookie_name>
4. Save and synchronize to Nodes
5. Generate and Propagate the Web Plugin
6. Then restart both Nodes

Hope this will be helpful!

What a long weekend, just to troubleshoot why the Group Authorization does not work in my Lotus Domino Quickr server. Actually it is just a silly mistake that I did when adding the group into that Place ACL. Basically these are the correct steps…

If you like to use qptool command, use this command:

“load qptool addmember -g parameter ..“; the ‘-g’ here means that the DN that we are adding is the DN for external group.

If you like to do it manually using the Quickr Manage Members GUI, just make sure that you select the “Group” radio button when searching and adding the search entries.

But, if it is already too late, just simply use “load qptool updatemember -targetg parameter” command to promote the DN to be Group External.

Hope this will help.

Cheers!!

Last weekend I hit the “Failed to Fetch” error during the WCM Syndication. After consulting to several IBM engineers, I finally managed to solve it.

This article shows you how to solve this issue.

This is the error that you will see in the

“SystemOut.logDepRef(id:e1e33e004d38843daddcbfa9d90c6c64 type: com.aptrix.pluto.cmpnt.FileResourceCmpnt nonDraft:true draft:false purged:false parentId:e1e33e004d38843daddcbfa9d90c6c64 timeStamp:1242648680000 stateUpdate: false versions:null) could not be found”

These are the steps to solve it:

1. Delete the existing syndicator-subscriber pair
2. Stop the portal server on the syndicator machine
3. Navigate to /WPSHOME/config
4. Run the /wpsconfig.bat wcm-reset-event-log task. This will essentially clear the data that the syndicator is using to send the content. Note that this is to be run inside the syndicator machine
5. You might also want to exclude the versions from the syndication by adding “deployment.noVersions=true” inside the WCMConfigService.properties in both syndicator and subscriber machines
6. Start the portal server at the syndicator machine
7. Re-create the syndicator – subscriber pair
8. Make sure that you rebuild the syndication once this has been done.

Hope this will help everyone!

Cheers!