WebSphere India

    We live in a world surrounded by devices now, it could be an alarm clock that wakes you up in the morning or a mobile phone that you always use. These devices form a important part of our life. Previously computing included only big enterprise servers and slowly moved towards personal computers. But Usage of Tablets, Smartphones are increasing now-a-days...Most of the businesses are looking at extending their business capabilities to mobile devices. To achieve this , they are building applications for mobile and also interacting with several other devices that consume, route or produce information.
 
    So Its now the time to connect everything together. People are connecting things as there are business opportunities in doing so. Now-a-days we are connecting several things to the enterprise, like temperature sensors, medical devices, power meters, etc. Some of them in the past have been connected using hard wiring. Now-a-days, we are seeing increasing use of networks such as cellphone infrastructure... We have started to think if people can talk, why not the devices...
 
    There are several types of applications that can now run on a mobile. Some of them are web based and some are native applications. Now we have applications that are even hybrid, ie native applications that utilize the browser interface to delivery content. A product from IBM that can be helpful to address the mobile needs is IBM Worklight. It can be used to develop hybrid applications.  IBM Worklight provides an open, comprehensive and advanced mobile application platform for smartphones and tablets, helping organizations of all sizes to efficiently develop, connect, run and manage HTML5, hybrid and native applications. Mobile messaging can be used in hybrid application to connect to the enterprise messaging backbone.
 
    HTTP has been standard way for several years now for web applications . But you need more than just HTTP. Mobile and the internet of things have additional challenges like emitting information from one to many, listening to events, pushing information, etc. To achieve this, IBM now provides reliable mobile access to the Enterprise. Its underpinned by MQ Telemetry Transport (MQTT) protocol. The product that will help address the needs for messaging is IBM WebSphere MQ. Its evolved a lot now and provides capabilities to move messages, interact between services, move files, integrate with Mobile, applications and even sensors. MQTT plays a important role in mobile messaging. It provides reliable transport, push notification, publish subscribe paradigm, and also converse battery and bandwidth,  IBM WebSphere MQ Telemetry provides mission-critical connectivity and intelligence by delivering, relevant near real-time data to intelligent decision making assets.
 
Following links provide you more information on this topic:
1. Eclipse Paho Project
2. MQDev Blog
3. WebSphere MQ Telemetry
4. IBM Worklight
   
Something interesting for the developers to think about now ... How are mobile applications different from the desktop or server applications? How applications targeted for small sensors interact with the enterprise?

Hi Webspherians

I want to share with you the basic steps of migration of derby/cloudscape database of websphere portal server into standard databases as Oracle or DB2.

 

1: Setting up Databases:

Followings are the 7 internal databases of Websphere Portal.

• release
• customization
• community
• jcr
• feedback
• likeminds
• wmm

 We need to create these 7 databases in the intended DB.(DB2/Oracle) by following script:

 

db2 "CREATE DB dbname using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"

db2 "UPDATE DB CFG FOR dbname USING applheapsz 2048"

db2 "UPDATE DB CFG FOR dbname USING app_ctl_heap_sz 1024"

db2 "UPDATE DB CFG FOR dbname USING stmtheap 8192"

db2 "UPDATE DB CFG FOR dbname USING dbheap 2400"

db2 "UPDATE DB CFG FOR dbname USING locklist 1000"

db2 "UPDATE DB CFG FOR dbname USING logfilsiz 1000"

db2 "UPDATE DB CFG FOR dbname USING logprimary 12"

db2 "UPDATE DB CFG FOR dbname USING logsecond 20"

db2 "UPDATE DB CFG FOR dbname USING logbufsz 32"

db2 "UPDATE DB CFG FOR dbname USING avg_appls 5"

db2 "UPDATE DB CFG FOR dbname USING locktimeout 30"

db2 "UPDATE DB CFG FOR dbname using AUTO_MAINT off"

 

replace dbname with RELEASE,JCR...etc

 

On DB2 client machine, run the following commands to catalogue the databases.

db2 "catalog db remote_db_name_release as release_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_community as comm_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_customization as cust_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_fdbkdb as fdbkdb_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_lmdb as lmdb_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_jcrdb as jcrdb_alias_name at node remote_db_node_alias"

db2 "catalog db remote_db_name_wmmdb as wmmdb_alias_name at node remote_db_node_alias"

 

2. Updating properties file: Update following properties files as per our databases.

wpconfig_dbdomain.properties

wpconfig_dbtype.properties

wpconfig.properties

wpconfig_sourceDb.properties

 

 3. Validating properties files: Run the following commands to validate entries of configuration properties done in previous step.

(These commands are for Unix plateform)

./WPSconfig.sh validate-database-connection-wps -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password

./WPSconfig.sh validate-database-connection-jcr -Djcr.DbPassword=password

./WPSconfig.sh validate-database-connection-feedback -Dfeedback.DbPassword=password

./WPSconfig.sh validate-database-connection-likeminds -Dlikeminds.DbPassword=password

./WPSconfig.sh validate-database-connection-wmm -Dwmm.DbPassword=password

./WPSconfig.sh validate-database-driver

Check the output of each command.

 4. Stop the Servers: Stop Websphere portal as well as application server by following commands:

• ./stopServer.sh WebSphere_Portal -user username -password password
• ./stopServer.sh server1 -user username -password password

5. Transfer the database: To transfer the database, perform this step:

1. Change to the directory portal_server_root/config.
2. Enter the following commands to run the configuration task.

./WPSconfig.sh database-transfer -Drelease.DbPassword=password-Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password 

check the output of the command.

Successful outcome of above command insures that Database transafer is successful.

6. Start Servers: Start Websphere portal as well as application server by following commands:

• ./startServer.sh WebSphere_Portal
• ./startServer.sh server1

Now you can Login to the Websphere portal and start exploring it more!

Cheers!
Pragati

 

Join members of the Business Process Manager V7.5 product team for the "BPMChat" Tweetchat.

Topic: Entitlements for IBM Business Process Manager V7.5
Date: June 2, 12-1PM EST
Hashtag: #bpmchat

Quotable quotes:
"You know, IBM Business Process Manager V7.5 is only days away from being available. Existing WebSphere Process Server And WebSphere Lombardi Edition customers should definitely participate in this tweetchat to learn how they can take advantage of V7.5" - Bill Lawton, IBM Product Manager

"IBM Business Process Manager is the most powerful BPM platform in the world. We will be sharing with customers why they should migrate to this new platform and understand how IBM is protecting their investment." - Trent Shupe, IBM Marketing Manager

Post your comments/questions ahead here

To learn more about Business Process Manager, click here

Courtesy: Krista Summit, IBM Social Media Strategist.