Creating a Server Profile fails while using a Roaming Profile

Technote (troubleshooting)


Problem(Abstract)

Attempts to launch the Profile Management Tool (PMT) from IBM Rational Application Developer for WebSphere Software or from the command line in order to create a WebSphere Application Server profile results in a failure if you use a Roaming Profile where your user home directory is accessed with a Universal Naming Convention (UNC) path.

Symptom

Launch the Profile Management Tool in one of the following two ways:

    • From the Command Line:


      C:\Program Files\IBM\SDP\runtimes\base_v[n]\bin\ProfileManagement\pmt.bat


      where n = 6,61,7,8 depending on the version of WebSphere Application Server for which you attempt to create the profile.
      Note that the path could differ, if you are using a standalone installation of WebSphere Application Server:

      <WebSphere>\AppServer\bin\ProfileManagement\pmt.bat


      OR
    • From the menu Windows > Preferences > Server > WebSphere Application Server > Run Profile Management Tool

    The error message PMT: An error has occurred. See the log file \\Redirected_Profile\PMT\workspace\configuration\log as in the following screen capture:

    and the referenced log file contains the following errors:


    eclipse.buildId=unknown
    java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr9-20101209_70480 (JIT enabled, AOT enabled)
    J9VM - 20101209_070480
    JIT - r9_20101028_17488ifx3
    GC - 20101027_AA
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
    Framework arguments: -jar startup.jar
    Command-line arguments: -jar startup.jar -os win32 -ws win32 -arch x86 -clean -dev C:\Program Files\IBM\SDP80\runtimes\base_v7\bin\ProfileManagement\..\..\lib\bootstrap.jar

    !ENTRY org.eclipse.update.configurator 2012-01-31 11:34:42.915
    !MESSAGE Problem in ConfigurationActivator.retrieveWebSphereBundles()

    !ENTRY org.eclipse.update.configurator 2012-01-31 11:34:42.993
    !MESSAGE java.lang.reflect.InvocationTargetException
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:611)
    at org.eclipse.update.internal.configurator.ConfigurationActivator.retrieveWebsphereSelectiveBundleData(ConfigurationActivator.java:592)
    at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:96)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:991)
    at java.security.AccessController.doPrivileged(AccessController.java:251)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:985)
    at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:966)
    at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:317)
    at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:329)
    at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1046)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:573)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:495)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:275)
    at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:455)
    at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:189)
    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:291)
    Caused by: java.lang.Exception: Problem processing metadata files
    at com.ibm.ws.bootstrap.SelectiveBundleMetadataMgr.ensureMetadataProcessed(SelectiveBundleMetadataMgr.java:679)
    at com.ibm.ws.bootstrap.SelectiveBundleMetadataMgr.getBundlesToInstall(SelectiveBundleMetadataMgr.java:197)
    ... 19 more
    Caused by: java.lang.IllegalArgumentException: URI has an authority component
    at java.io.File.<init>(File.java:379)
    at com.ibm.ws.bootstrap.SelectiveBundleMetadataMgr.retrieveOsgiConfigDir(SelectiveBundleMetadataMgr.java:698)
    at com.ibm.ws.bootstrap.SelectiveBundleMetadataMgr.ensureMetadataProcessed(SelectiveBundleMetadataMgr.java:665)
    ... 20 more


Cause

Profile Management Tool needs access to a local resource to store configuration files. It cannot store such files on a UNC path.

UNC paths begin with \\ two backslashes) and take the form:

\\Computer_name\Share_name

Resolving the problem

To resolve this issue:

  1. Open the following config.ini file with a text editor:

    C:\Program Files\IBM\SDP\runtimes\base_v[n]\bin\ProfileManagement\configuration\config.ini
    Note that the path could differ, if you are using a standalone installation of WebSphere Application Server:
    <WebSphere>\AppServer\bin\ProfileManagement\eclipse64\configuration\config.ini


  2. Edit the following lines:

    osgi.instance.area.default=@user.home/PMT/workspace
    osgi.configuration.area=@user.home/PMT/workspace/configuration


    The @user.home variable refers to the current user's home directory, which in this case resolves to a UNC Path.

  3. Change the lines to a local path, such as the following:

    osgi.instance.area.default=c\:/temp/PMT/workspace
    osgi.configuration.area=c\:/temp/PMT/workspace/configuration

    • You can choose any directory on a local hard disk drive.
    • The data does not need to be preserved; you can delete it after PMT terminates execution.
    • Ensure to use forward slashes /instead of backslashes \ as path delimiters.

  4. Save the file and retry operation.

Related information

RFE: Support UNC Paths for the creation of WAS Profiles

Cross reference information
Segment Product Component Platform Version Edition
Software Development Rational Software Architect for WebSphere Software Profiling / Performance Analysis Windows 7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5, 7.5.5.1, 7.5.5.2, 7.5.5.3, 7.5.5.4, 7.5.5.5, 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.4.1, 8.0.4.2, 8.5, 8.5.1, 8.5.5, 8.5.5.1, 9.0, 9.0.0.1, 9.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Application Developer for WebSphere Software
Server Runtimes

Software version:

7.5, 7.5.1, 7.5.2, 7.5.3, 7.5.4, 7.5.5, 7.5.5.1, 7.5.5.2, 7.5.5.3, 7.5.5.4, 7.5.5.5, 8.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.4.1, 8.0.4.2, 8.0.4.3, 8.5, 8.5.1, 8.5.5, 8.5.5.1, 9.0, 9.0.1, 9.1, 9.1.0.1

Operating system(s):

Windows

Reference #:

1584343

Modified date:

2014-08-27

Translate my page

Machine Translation

Content navigation