.*iPhone.*
xdime
pdaview
Apple
Apple iPhone
.*Android.*
xdime
pdaview
Google
Google
.*BlackBerry.*
xdime
pdaview
RIM
RIM
.*iemobile.*
xdime
pdaview
Microsoft
Internet Explorer
Warehouse for various notes, scripts, code samples, tips/tricks, etc. relating to different technologies like WebSphere Application Server (WAS), WebSphere Portal, Java, Java EE, DB2, etc.
Friday, October 21, 2011
User Agent String for iPad 2
Mozilla/5.0 (iPad; U; CPU OS 4_3 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Version/5.0.2 Mobile/8F191 Safari/6533.`8.5
Labels:
Mobile Redirection,
MPA,
WebSphere Portal,
WEMP
How to midy Supported Client List using XML Access
There are 3 steps to changing the supported client list using XML Access (xmlaccess) utility:
1. Take export of the entire portal using the following command and input file:
Command
Export File
2. Create Update_SupportedClients.xml file as follows:
Import File
Change the values of the "objectid" from the file (Result_File.xml) exported in the step 1 above. Change the "ordinal" and any other value as per your requirements.
3. Import the changes into Portal using following command:
Command
1. Take export of the entire portal using the following command and input file:
Command
xmlaccess -in Export.xml -user userid -password password -url portal.example.com:10039/wps/config -out Result_File.xml
Export File
<?xml version="1.0" encoding="UTF-8"?>
<request
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd"
type="export"
export-users="false">
<portal action="export"/>
</request>
<request
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd"
type="export"
export-users="false">
<portal action="export"/>
</request>
2. Create Update_SupportedClients.xml file as follows:
Import File
<?xml version="1.0" encoding="UTF-8"?>
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd" type="update">
<portal action="locate">
<client action="update" domain="rel" markup="html" name="Default HTML Client" objectid="M_0000000000000000000000C010" ordinal="75">
<useragent-pattern>.*</useragent-pattern>
</client>
<client action="update" domain="rel" markup="xdime" name="Default XDIME Client" objectid="M_VBL70VO20G0000I1D5CPPM3043" ordinal="50" uniquename="mwp.default.xdime.client">
<useragent-pattern>.*</useragent-pattern>
</client>
</portal>
</request>
<request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_1.4.xsd" type="update">
<portal action="locate">
<client action="update" domain="rel" markup="html" name="Default HTML Client" objectid="M_0000000000000000000000C010" ordinal="75">
<useragent-pattern>.*</useragent-pattern>
</client>
<client action="update" domain="rel" markup="xdime" name="Default XDIME Client" objectid="M_VBL70VO20G0000I1D5CPPM3043" ordinal="50" uniquename="mwp.default.xdime.client">
<useragent-pattern>.*</useragent-pattern>
</client>
</portal>
</request>
Change the values of the "objectid" from the file (Result_File.xml) exported in the step 1 above. Change the "ordinal" and any other value as per your requirements.
3. Import the changes into Portal using following command:
Command
xmlaccess -in Update_SupportedClients.xml -user userid -password password -url portal.example.com:10039/wps/config -out Result_File.xml If everything went well then you will see success message at the end.
Labels:
Mobile Portal Accelerator,
MPA,
WebSphere Portal,
WEMP
Wednesday, October 19, 2011
Redirecting all users using Mobile devices to a specific URL
To redirect all the incoming requests from mobile devices to a sub-directory or a specific URL in IBM HTTP Server follow below steps:
Open C:\IBM\HTTPServer\conf\httpd.conf file in edit mode.
1. Un-comment following live in the file by removing "#" from the front of the line.
#LoadModule rewrite_module modules/mod_rewrite.so
2. Enable rewrite engine by adding following line to the end of the file:
RewriteEngine on
3. Add rewrite condition for the detecting mobile devices after the above line using the below example:
RewriteCond %{HTTP_USER_AGENT} "android|blackberry|ipad|iphone|ipod|iemobile|opera mobile|palmos|webos|googlebot-mobile" [NC]
4. Add rewrite rule for redirecting the user to specific URL after the above line using the below example
RewriteRule ^(.*)$ http://mobile.example.com/wps/portal [L,R=302]
5. Save the file
6. Restart IBM HTTP Server.
Now all user requests will be redirected to "http://mobile.example.com/wps/portal" sub URL.
Enable user redirection in IBM HTTP Server 7.0
To redirect all the incoming requests to a sub-directory or a specific URL in IBM HTTP Server follow below steps:
Open C:\IBM\HTTPServer\conf\httpd.conf file in edit mode.
1. Un-comment following live in the file by removing "#" from the front of the line.
#LoadModule rewrite_module modules/mod_rewrite.so
2. Enable rewrite engine by adding following line to the end of the file:
RewriteEngine on
3. Add rewrite rule after the above line using the below example:
RewriteRule ^/$ wps/portal [L,R]
4. Save the file
5. Restart IBM HTTP Server.
Now all user requests will be redirected to "wps/portal" sub URL. You can redirect the user to another website also using the same method but in that situation you have to provide full URL starting with Http://...
Wednesday, August 10, 2011
WCM Contect Access Error using API - WCM_Workspace W IWKCW1005X: The Member: UserX Could not be found in the User Repository. Reason: UserX
[8/10/11 13:48:23:737 CDT] 0000006e WCM_Workspace W IWKCW1005X: The Member: UserX Could not be found in the User Repository. Reason: UserX
[8/10/11 13:48:23:753 CDT] 0000006e SystemOut O exception is- com.ibm.workplace.wcm.api.exceptions.AuthorizationException: IWKPY1015X: Unauthorized access by {PrincipalInformation: {dn: anonymous_user, memberId: anonymous_user_id, displayName: , name: , locale (thread): en_US, isValidUser: true, isUser: Type: User, isUserLazyLoaded: false}, 1, {false, {userAccess={}}, {editorAccess={}}, {managerAccess={}}, [anonymous_user%anonymous_user_id, all_users%all_users_group_id, anonymous_user%anonymous_user_id]}} - IWKPY1016X: Unauthorized access on Company Overview by [anonymous portal user]
Encountered above exception when I was trying to access WCM content using API calls from my portlet. After researching for long and spending multiple nights figuring the reason behind this exception I found that I need to give proper access rights to all the users under "Contributor" tab of the Portal Content > Web Content Libraries > Library Name.
Click on the button with "key" to open the resource permissions for the library. Then click on the button with "key" against "Contributor". Add "All authenticated Portal Users" and "Anonymous Portal Users" to the permissions.
This will resolve the above problem.
More information is available on the below link:
PM42031: REFERENCE PROBLEM IN INLINE EDITING WITH THE JSR-286 WEB CONTENT VIEWER
[8/10/11 13:48:23:753 CDT] 0000006e SystemOut O exception is- com.ibm.workplace.wcm.api.exceptions.AuthorizationException: IWKPY1015X: Unauthorized access by {PrincipalInformation: {dn: anonymous_user, memberId: anonymous_user_id, displayName: , name: , locale (thread): en_US, isValidUser: true, isUser: Type: User, isUserLazyLoaded: false}, 1, {false, {userAccess={}}, {editorAccess={}}, {managerAccess={}}, [anonymous_user%anonymous_user_id, all_users%all_users_group_id, anonymous_user%anonymous_user_id]}} - IWKPY1016X: Unauthorized access on Company Overview by [anonymous portal user]
Encountered above exception when I was trying to access WCM content using API calls from my portlet. After researching for long and spending multiple nights figuring the reason behind this exception I found that I need to give proper access rights to all the users under "Contributor" tab of the Portal Content > Web Content Libraries > Library Name.
Click on the button with "key" to open the resource permissions for the library. Then click on the button with "key" against "Contributor". Add "All authenticated Portal Users" and "Anonymous Portal Users" to the permissions.
This will resolve the above problem.
More information is available on the below link:
PM42031: REFERENCE PROBLEM IN INLINE EDITING WITH THE JSR-286 WEB CONTENT VIEWER
Wednesday, July 6, 2011
Datasource Isolation Levels in WebSphere Application Server (WAS)
WebSphere Application Server (WAS) 6.0.2 and higher provide a new custom property webSphereDefaultIsolationLevel. This property can take one of the four values as listed below:
a) 8 -> TRANSACTION_SERIALIZABLE -> Repeatable Read (RR)
b) 4(default) -? TRANSACTION_REPEATABLE_READ -> Read Stability (RS)
c) 2 -> TRANSACTION_READ_COMMITTED -> Cursor Stability (CS)
d) 1 -> TRANSACTION_READ_UNCOMMITTED -> Uncommitted Read (UR)
a) 8 -> TRANSACTION_SERIALIZABLE -> Repeatable Read (RR)
b) 4(default) -? TRANSACTION_REPEATABLE_READ -> Read Stability (RS)
c) 2 -> TRANSACTION_READ_COMMITTED -> Cursor Stability (CS)
d) 1 -> TRANSACTION_READ_UNCOMMITTED -> Uncommitted Read (UR)
Labels:
Data Source,
DB2,
SQL,
WAS,
WebSphere,
WebSphere Application Server,
WebSphere Portal
Subscribe to:
Posts (Atom)