Thursday, October 31, 2013

IBM Business Process Manager (BPM) 8,8.0.1 and 8.5 Training

Hey Everyone

The BPM training for V8,8.0.1 and 8.5 is available from the IBM Website.URLs listed below:


http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.ibpmgr/ibpmgr/8.0/ProcessDesigner.html

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.ibpmgr/ibpmgr/8.5/ProcessDesigner.html

Your in WebSphere
Jerome Slinger

WAS 8 and 8.5 Training Labs have been Released

Hi my fellow WebSpherians

Don't forget to visit the WebSphere Application Server version 8 and 8.5 training labs.

Attached the URLS :


http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v8/was/8.0/Labs.html

http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.was_v8/was/8.5/Labs.html

Your in WebSphere
Jerome

Thursday, October 24, 2013

Caching Issue in WebSphere Portal version 6.1, 7.0 and 8.0

Currently Committed database setting - Applies to DB2 v9.7 or higher and WebSphere Portal version 6.1 and 7.0
 
DB2 V9.7 introduced a new default behaviour for isolation level cursor stability (CS) (see http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.config.doc/doc/r0053556.html).
In WebSphere Portal this has implications for the cache invalidation strategy related to transactions. The new DB2 default behaviour for isolation level cursor stability (CS) is to NOT block code that wants to read data which is still being worked on in an uncommitted transaction in another thread (DB2 returns the result, as if the other transaction would not exist). But WebSphere Portal version 6.1 and 7.0 cache invalidation and refill strategies rely on the blocking at database level. With the new 'currently committed' default setting, stale data in Portal caches can occur.

Starting with Portal version 8.0 the setting of CUR_COMMIT to ENABLED is supported.

Besides the fact that CUR_COMMIT must be set to DISABLED for WebSphere Portal version 6.1 and 7.0, WebSphere Portal development does not expect a performance degradation when changing the value of CUR_COMMIT from ENABLED to DISABLED. For some scenarios with long database transactions, it could be that response times increase due to additional waits for updated data.

The setting of CUR_COMMIT is applied at database level. Therefore it is required to set CUR_COMMIT to DISABLED for the Portal database(s), containing the Portal database domains release, community, customization, jcr, feedback, and likeminds.

Disabling CUR_COMMIT in DB2 Version 9.7:

Ask your DB2 administrator to ensure that CUR_COMMIT is disabled by carrying out the following steps (for each of the Portal databases):
    1. Connect to the runtime database:
      $ db2 connect to
      where represents the name of the database.
    2. List the CUR_COMMIT parameter:
      $ db2 get db cfg show detail | grep CUR_COMMIT
      The output should look like this:
      Currently Committed (CUR_COMMIT) = DISABLED DISABLED
    3. If the values are anything other than two times DISABLED (one for the current setting used, the other for the delayed setting specified in the configuration), change the value to DISABLED:
      $ db2 update db cfg using CUR_COMMIT DISABLED
    4. Close the database connection:
      $ db2 connect reset
    5. Check that no other application is connected to the database,to make the change effective (This e.g. requires to stop the Websphere Portal Server that uses the database). List the connected applications like this:
      $ db2 list applications for db
      where represents the name of the database.
      The output should look like this:
      SQL1611W No data was returned by Database System Monitor.
    6. Ensure that the settings are correct by repeating the steps 1. and 2.
Full technote and source : http://www-01.ibm.com/support/docview.wss?uid=swg27037929&myns=swgws&mynp=OCSSHRKX&mync=E#!

Friday, October 11, 2013

Migration to an empty Portal 6.1.x will not work.

Hi All

I am posting this in reply to so many questions that came in surrounding migration.

Please note that you can experience this in 7.0 and 8.0.

 

Technote (FAQ)

Question

One is often drawn into a speculation that migration onto an empty portal will work. Migration to an empty portal will not work.

Answer

Migration to an empty portal will often fail because of various reasons. The empty portal typically contains a few content-nodes, application roles and certain other virtual resources and no other portal artifacts like portlets, pages, themes, skins. The migration scripts are typically looking for these artifacts to do the migration. And hence the failure.

Source : http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21383211


 

Tuesday, October 8, 2013

Wpcollector tool, new in WebSphere Portal 7.0 and 8.0

Wpcollector is a new command line tool that automates the collection of portal logs and configuration files and optionally assists the customer with sending those files to IBM Support, saving valuable time. Using automated log collection early in the PMR life cycle can greatly reduce the number of doc requests that are made by Support. Wpcollector is an excellent tool for those customers that are not able to download and install ISA Lite in their portal environment.

Wpcollector is delivered with WebSphere Portal beginning with the 7.0 release. A significant difference between wpcollector and ISA Lite is that ISA Lite will automatically enable the correct traceString and collect the appropriate files based on the problem type selected in the ISA Lite GUI. Wpcollector, however, does not currently have a mechanism for the user to specify the problem type. Therefore, if tracing is required for the problem, the customer must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. Similarly, because wpcollector consists of only 1 script, it collects all of the files for all of the various problem types each time the tool is run.

To run wpcollector, please follow the steps, below:

  • If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below:

  • If using Microsoft Windows, Unix/Linux, or IBM i, run the following script from the /PortalServer/bin/ directory to begin the collection:

      Windows: wpcollector.bat
      Unix/Linux: wpcollector.sh
      i: wpcollector.sh
      Tip: To specify the option for automatically sending the collection to IBM Support via FTP, use the "pmr" parameter. This will associate the collection with the PMR (Problem Management Record) specified. Be sure to format the number using either periods or commas. For example:
      wpcollector.bat -Dpmr=nnnnn.bbb.ccc (nnnnn=PMR number, bbb=branch, ccc=country code)
      Tip: To specify the option for collecting files for the Deployment Manager profile, use the "dmgr.root" parameter. For example:
      wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile
  • If using IBM z/OS, proceed as follows:

      Start the WebSphere Portal Customization Dialog.
      In the Portal configuration panel, select Collect Diagnostics.
      Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS).
      Tip: To specify the option for automatically sending the collection to IBM Support via FTP, respond to the "Transmit PMR Data" prompt with "Y" in the ISPF panel as follows:
      Transmit PMR data to IBM .................................: Y
      Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.

  • If the automatic send/FTP option was not specified, a manual transfer of the collection to IBM will be necessary. Locate the wp.mustgather-.zip file or the -wp.mustgather-.zip file in the <wp_profile_root>/filesForAutoPD/ directory and follow the instructions in "Exchanging information with IBM Technical Support for problem determination" to manually FTP the collection to IBM. If using z/OS, there may be additional z/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them. 
Do not underestimate this tool as when raising a PMR it is best to ensure that IBM support have all the information they need.

Happy Trails
Jerome Slinger


Friday, October 4, 2013

Installing WebSphere Application Server Version 8 or later

Before you begin

If Installation Manager is running, stop it.

About this task

You can install IBM WebSphere Application Server, version 8.0 at the same time that you install Rational® Software Architect, version 8.0 or by itself. Unlike the other WebSphere Application Server test environment extensions, WebSphere Application Server, version 8.0 does not share the same installation location and package group as Rational Software Architect, version 8.0.

Procedure

  1. If Rational Software Architect is running, stop the software.
  2. Depending on your user ID, complete one of the following steps:
    • If you are installing as an Admin:
      1. Start the launchpad.
      2. Click Install IBM Rational Software Architect.
    • If you are installing as a non-Admin: Start the installation from the Setup disk by running the userinst program.
  3. Install or update IBM Installation Manager.
    1. On the first page of the Install Packages wizard, click Check for Other Versions and Extensions to install the latest available version. If a newer version is available, it is automatically selected for installation. Click Next.
    2. On the Licenses page, read the license agreements for IBM Installation Manager. If you agree to the terms of all of the license agreements, click I accept the terms in the license agreements and then click Next.
    3. If Installation Manager is not already installed: On the location page, in the Installation Manager Directory field, type the path type the path for the directory where you want to install Installation Manager or accept the default path and then click Next.
    4. On the Summary page, review your choices before starting the installation process. If you want to change your selections, click Back to return to the previous pages. When you are satisfied with your selections, click Install.
    5. When the installation process completes, click Restart Installation Manager. Installation Manager closes and restarts.
  4. In the IBM Installation Manager window, click Install. The Install Packages wizard opens.
  5. On the first page of the Install Packages wizard, select Application Server 8.0.0.0 and then click Next.
  6. You can install updates at the same time that you install the base product package. To search for updates to the packages, click Check for Other Versions and Extensions. Installation Manager searches for updates at the predefined IBM update repository for the product package. It also searches any repository locations that you have set.
  7. To learn more about the packages that you can install, click the package name. A description of the package is displayed in the Details pane. If additional information about the package is available, a More info link is included at the end of the description text. Click the link to display the additional information in a browser.
  8. Click Next.
  9. On the Licenses page, read the license agreements for the selected packages. On the left-hand side of the License page, click each package version to display its license agreement.
    1. If you agree to the terms of all of the license agreements, click I accept the terms of the license agreements.
    2. Click Next to continue.
  10. Depending on whether you have already used Installation Manager to install software, you might have to select the shared resources directory on the Location page. Type the path for the in the Shared Resources Directory field, or accept the default path and then click Next to continue. If you are installing on Linux, ensure that you do not include any spaces in the directory path. The shared resources directory contains resources that can be shared by one or more package groups.
    Important: You can specify the shared resources directory only at the time that install Installation Manager. Use your disk with the most available space for this to help ensure adequate space for the shared resources of future packages. You cannot change the directory location unless you uninstall all packages.
  11. On the Location page, type the path for the installation directory for the package group and then click Next. (If you are installing on Linux, ensure that you do not include any spaces in the directory path.) The name for the package group is created automatically.
    Important: If you are installing as with a non-Admin user ID on Microsoft Windows Vista, Windows 7, or Windows Server 2008: You must choose an installation location the product that is not in the Program Files path (C:\Program Files) if you want to be able to run the application as a non-Admin user.
    If you select an installation directory that is in the Program Files path, then you must run the application as the administrator. To run as administrator, right-click the program shortcut and click Run as administrator.
  12. On the Features page, select the features that you want to install. Click the feature to see more information about it in the Details section of the page. When you are finished, click Next.
  13. On the Summary page, review your choices before installing the product package. If you want to change the choices that you made on previous pages, click Back, and make your changes. When you are satisfied with your installation choices, click Install to install the package. A progress indicator shows the percentage of the installation completed.
  14. When the installation process completes, select to star Profile Management Tool and then click Finish.

What to do next

  • Create a developer profile for WebSphere Application Server, version 8.0.
  • If not installed already, install IBM Rational Software Architect, version 8.0. Ensure that you select the WebSphere Application Server, version 8.0 development tools feature.
Reference : http://pic.dhe.ibm.com/infocenter/rsahelp/v8/index.jsp?topic=%2Fcom.ibm.xtools.installation.rsaws.doc%2Ftopics%2Ft_install_was8.html