How to Install plug-ins in IBM UrbanCode Build


  1. Download the installation files for one or more plug-ins from the following site: Do not extract the compressed files.
  2. Load the plug-ins:
    1. From the IBM UrbanCode Build user interface, click the System tab.
    2. In the Server group, click Plug-ins.
    3. On the Plugins page, Browse and locate the plug-in installation file and then click Open.
    4. On the Plugins page, click Load.


After the upload to the server is complete, the plug-in is listed on the Plugins page and available for immediate use.

Uninstalling a plug-in

To uninstall a plug-in, click System > Plug-ins, locate the plug-in, and then click the Delete icon.

Note: Before uninstalling a plug-in, verify that it is no longer in use. Deleting a plug-in which is being used by existing processes causes those processes to be invalid.

Tagged : / / / /

Upgrade Artifactory from Open-Source (OSS) to PRO?

The upgrade process from OSS to PRO is the same one that is used for upgrading from any Artifactory version to the latest version;
The procedure to upgrade Artifactory depends on your installation type. There are following installation types:

  • ZIP file
  • RPM
  • Debian
  • Docker

In this tutorials, I am talking about Zip file Based installation only.

Before You Proceed, You must do following.

1. Take a Backup of System config using “System Export”
Artifactory can export and import the whole Artifactory server: configuration, security information, stored data and metadata. The format used is identical to the System Backup format. This is useful when manually running backups and for migrating and restoring a complete Artifactory instance (as an alternative to using database level backup and restore).

Please follow the instructions out here

2. Back up your database.

3. JDK Version – From version 4.0, Artifactory requires JDK 8. If your current version is v3.x, before you upgrade to Artifactory 5.x, please make sure you install JDK 8 and update your JAVA_HOME environment variable to point to your JDK 8 installation.

4. Repositories with Multiple Package Types – From version 4.0, Artifactory will only index, and work with corresponding clients for single package type repositories. If your current version is 3.x and the installation includes repositories that support multiple package types, you need to migrate them to single package type repositories.

Upgrading from version 4.x or 5.x to the latest version is a simple procedure.

Step 1 – Unzip the Artifactory distribution archive.
Step 2 – If the $ARTIFACTORY_HOME/tomcat/conf/server.xml has been modified keep it in a temporary location.
Step 3 – Backup files to a temporary location according to the conditions described below:

  • In all cases, backup $ARTIFACTORY_HOME/bin/artifactory.default
  • If Artifactory is configured to work with a database that is not Derby, backup the $ARTIFACTORY_HOME/tomcat/lib/<JDBC> driver.

Step 4 – Remove the following files and folders from your $ARTIFACTORY_HOME folder:

  • webapps/artifactory.war
  • webapps/access.war
  • tomcat
  • bin
  • misc

Step 5 – Replace the removed files and folders with the corresponding ones from the new unzipped version.

Step 6 – Any files that were stored in temporary locations should now be returned to their original location under the new installation.

Step 7 – If you installed Artifactory as a service, you now need to run the service

  • For a Linux service, browse to $ARTIFACTORY_HOME/bin and execute the following command as root: $ARTIFACTORY_HOME/bin/ [USER [GROUP]]
  • For Windows service, browse to %ARTIFACTORY_HOME%\bin. First uninstall the service by running uninstallService.bat, then reinstall the service by running installService.bat. You can now run the service through the Windows UI or as described in Running Artifactory.


Tagged : / / /

Upgrade Registry Type 7.0 SP3

msiexpert created the topic: Upgrade Registry Type 7.0 SP3
Hi there,

after moving our Sharepoint and Database to another server (with changing the servername), I have the problem, that after installing 7.0 SP3 from scratch, the process “Upgrade Registry Types” in the Repository Manager is still pending no matter how often I click on “Run”
All other parts or modules of WPS are working well.

Any help is highly appreciated.

applicationPackaging replied the topic: Re: Upgrade Registry Type 7.0 SP3
Check the Altiris knowledgebase ( ) as there are some articles about repository manager issues which may help. If that does not solve your problem, then I would recommend making a call to Wise support as they have more information internally on these sorts of issues and may be able to help you solve this quickly.
I assume you have checked the sharepoint for INI files in case of any hard coded UNCs to the old server name. If you have SQL query skills then you could also check the Wise sql databases for any references to the old server.

Tagged :

Special Upgrade for WISE Installation Studio customers

pgadmin created the topic: Special Upgrade for WISE Installation Studio customers
This announcement originally appeared in a SoftVelocity newsgroup and is reposted here as a courtesy for WISE Installation Studio customers.

“If you are still using the WISE Installation System to develop your installations, you probably know that Symantec announced the
end-of-availability of WISE Installation Studio and WISE Installation Express. An era comes to an end.

Symantec does no longer accept orders for new licenses of WISE Installation Studio or WISE Installation Express. In addition, Symantec does no longer accept renewals for maintenance agreements related to WISE Installation Studio.

If you are concerned your WISE product doesn’t support your software deployment requirements, consider a jump to SetupBuilder Developer Edition.

Looking to target Windows 7, Windows Vista and Windows Server 2008? We’ve got you covered! We are committed to providing you with support for the latest advancements in installation, deployment and operating system technology!

Discover why more and more Wise users are making the switch to SetupBuilder:

For users who want to move over from WISE Installation Studio to SetupBuilder, there is currently a special offer:

Switch to SetupBuilder 7 Developer Edition including a full 1-year maintenance and support subscription plan and pay only $245 instead of $399.

This special offer expires June 30, 2010

Contact our Sales at to save 40% off your move to SetupBuilder Developer Edition.

Note: Special offer only available to customers moving over from WISE Installation Studio, providing proof of ownership.

Tagged :

SonarQube Upgrade, Backup and Restore Process | SonarQube Tutorial



SonarQube Upgrade, Backup and Restore Process


Today I will share the steps to upgrade from the SonarQube version 5.X to SonarQube version 6.X. We have upgrade guide which can be found but its not complete guide thus I am sharing the steps as follows which can be followed for the production server as well.  As practice shared on the oficial guide that before upgrading to the next major release, you must upgrade to know LTS e.g
Example 1 : 4.2 -> 6.1, migration path is 4.2 -> 4.5.7 LTS -> 5.6 LTS -> 6.1
Example 2 : 5.1 -> 5.6, migration path is 5.1 -> 5.6


Upgrading across multiple versions is handled automatically. However, if in your migration path you have an LTS version, you must first migrate to this LTS and then migrate to your target version.


Remember that SonarQube upgrade procedure does not have a rollback procedure, so it is mandatory that you take a full backup of the system before performing the upgrade.


Process 1: Steps to Take a Full Backup of SonarQube Server?

Step 1 – Stop the production server
$SONAR_HOME/bin/linux-x86-64/ stop
Step 2 – Backup the production database e.g mysql db
> mysqldump –opt -Q -h localhost -u username–password=’password’ databasename | gzip -9 > databasename.gz
Also, there is one tool which has been available to take the backup of database.
Step 3 – Backup the $SONAR_HOME directory
> zip -r $SONAR_HOME
Step 4 – List of plugins installed
Be mindful that $SONAR_HOME/extensions/plugins directory where you can get the list of plugins installed.
Step 5 – List of custom coding rules installed
Be mindful that $SONAR_HOME/extensions/rules directory where you can get the list of custom coding rules.
Step 6 – List of configurations used
Be mindful that $SONAR_HOME/config directory where you can get and wrapper.conf file which has all the current configurations and setup.
Step 7 – Re-start the production server
$SONAR_HOME/bin/linux-x86-64/ start
Step 8: Keep the and databasename.gz to the safe location.


Process 2: SonarQube server Upgrade process.

Following are the steps to be followed to upgrade the SonarQube server.
Step 1: Stop your old SonarQube Server.
Step 2: Install/Configure a most latest version of SonarQube 
Install/Configure a most latest version of SonarQube Server in another location. The instructions is shared here (
Step 3: Install the your required plugins/extensions compatible with your version of SonarQube. The Instructions is shared here.(
Step 4: Update the contents of and wrapper.conf files (in NEW_SONARQUBE_HOME/conf) with the settings of the related files in the OLD_SONARQUBE_HOME/conf directory (web server URL, database, ldap settings, etc.). Do not copy-paste the old files.
If you are using the Oracle DB, copy its JDBC driver into NEW_SONARQUBE_HOME/extensions/jdbc-driver/oracle
Step 5: Start your new SonarQube Server
$SONAR_HOME/bin/linux-x86-64/ start
Step 7: Verify the SonarQube Upgrade.


Note – SonarQube as a Linux or Windows Service
If you use external configuration, such as a script or Windows Service to control your server, you’ll need to update it to point to NEW_SONARQUBE_HOME.
In case you used the InstallNTService.bat to install SonarQube as a Windows Service, run the OLD_SONARQUBE_HOME/bin/…/UninstallNTService.bat before running the InstallNTService.bat of the NEW_SONARQUBE_HOME.
If you install SonarQube with Sql Server, it is better to chose Latin1_General_CS_AS as collation to avoid problems.


Some Well known Troubleshooting after upgrades.
Issues – Sonarqube upgrade 5.6 to 6.1, test coverage measue is missing
Solution – You might be missing the Sonar-5.6 did not need those.
Issues – Some unknown issues
Solution – Whenever you have problem with SonarQube do not forget to read the log, because only in the log you can understand the real cause of errors.


Tagged : / / / / / / /

IBM Rational ClearCase Version 7.1.1 release | Rational ClearCase New Version


IBM Rational ClearCase Version 7.1.1 release

This information provides a brief description of the new features and restrictions in IBM Rational® ClearCase® Version 7.1.1
What’s New

For a list of new features available in this release, see What’s New
The Rational ClearCase Version 7.1.1 announcement is available at See the announcement for the following information:

Detailed product description, including a description of new functions
Product-positioning statement
Packaging and ordering details
International compatibility information

System requirements

For information about hardware and software compatibility, see the detailed system requirements document at .
Installing Rational ClearCase Version 7.1.1
For installation instructions, see this topic in the information center:

Known problems

Known problems are recorded in individual documents in the Support knowledge base. As problems are discovered and resolved, the knowledge base is updated and maintained with new information. By searching the knowledge base, you can quickly find workarounds or solutions to problems. To learn about the known limitations and problems in this update, and any workarounds that are available, see:
iFixes and Fixpacks
To learn about features and fixed defect fixes in Fixpack and iFixes:

Go to
Click Support & downloads
In the Select product or service type for support box, select the software category and then the product category.
Under Choose your task on the left side, click Downloads.
In the Featured download links box, click View all download links.
Click the link for an iFix or Fixpack.

Source: Click here

Tagged : / / / / / / / / / / / / / / / / /

Apache Subversion 1.7 has Arrived | What’s new in Subversion 1.7 ?


Apache Subversion 1.7 has Arrived

Subversion 1.7.0 has been officially released today.  With the release of Subversion 1.7 comes the release of Subversion Edge 2.1.0.  This release of Subversion Edge brings you the server binaries for Subversion 1.7.0 as well as the latest release of Apache httpd.  In addition to the inclusion of the Subversion 1.7 server binaries this release of Subversion Edge brings a number of other nice improvements including the addition of a complete 64-bit Windows binary stack.  As with all previous Subversion Edge releases you can simply update your existing installation from the Subversion Edge web console.  There are no other special considerations, the update mechanism handles all details.

I encourage all users to update their Subversion Edge servers to this release so that you and your users can enjoy the new features brought from this release as well as the improved performance and fixes that comes with Subversion 1.7.  Look for updates to your favorite Subversion clients to follow shortly.


Tagged : / / / / / / / / / / / / / / / /

Perforce New Version , Perforce 2011.1 released | Perforce 2011.1 Overview


Perforce 2011.1 released 11/07/2011

Perforce Release 2011.1 is now available. Check for platform and component availability.


Tagged : / / / / / / / / / / / / / / / /

Stable CVS Version 1.11.23 Released, What’s new in Perforce CVS 2011.1, let’s find?


Stable CVS 1.11.23 has been released. Stable releases contain only bug fixes from previous versions of CVS. This version includes an efficiency fix that reduces checkouts of very old revisions from an O(n^2) operation to an O(n) one, as well as yet another Windows file time stamp handling fix (bug #22781), and some other minor fixes and efficiency improvements. We recommend this upgrade for all CVS clients and servers!

Please take a look at the NEWS file from the CVS source distribution and the CVS 1.11.23 manual for more information about the changes contained in this release.

CVS can be downloaded from the GNU download server within four hours of this announcement or one of the mirrors after 24 hours or so (make sure to check the ”’non-gnu”’ directory on the mirrors). (This release may be obtained from Savannah download server prior to appearing on the GNU download server, but please don’t use the already heavily loaded Savannah download server unless you have to.) For other ways to obtain CVS, please read How to get GNU Software.


Tagged : / / / / / / / / / / / / / / / / / / / /

Sonar team released Sonar Maven Plugin 1.0-beta-2


The Sonar team is pleased to announce the release of Sonar Maven Plugin, version 1.0-beta-2.

It makes configuration easier when using a repository manager like Archiva or Nexus. Indeed no additional settings are required anymore ! Let’s remind that the version 1.0-beta-1 needs to declare a mirror in maven settings or to add a new repository to the manager.
This improvement requires Sonar 2.2+. It is automatically disabled when using sonar 2.1 or less. Upgrading to this version should be automatic if the shortcut “mvn sonar:sonar” or the hudson plugin are used.


Tagged : / / / / / / / / / / / / / /