Unleash Your Product Lifecycle Resources

Many of your product lifecycle resources are locked away in vendor proprietary databases.  This often prevents them from being reused and often results in wasted duplication and as a results longer times to market.   I think IBM and Rational have come up with an interesting way to make these resources be available in an open and scalable way using OSLC, Tracked Resource Set (TRS) Provider using a Linked Data approach and standards.   To accomplish this resources must be exposed using Web Application/Sever.  So traditional client only or file based tools require a Web Server be build or these files be hosted on a one that supports being a Tracked Resource provider like Rational Asset Manager that can do that for Word, PDF, Excel and other file based artifacts.   Or you can build your own using this TRS Software Development Kit (SDK)  Many of the IBM Rational Tools already provide support for Tracked Resources.  I recently published which ones here.  The same rules apply though so for DOORS you must utilize DOORS Web Access to expose your as searchable tracked resources.  For Rhapsody you must utilize Rhapsody Design Manager to expose your Design Elements as searchable tracked resources.

Here are the high level steps to expose these different servers as TRS providers.

  1. If the Rational Team Concert, Rational Quality Manager, etc. project area is on a separate RTC application on a separate JTS server you must create a JTS OAuth Friends relationship between the two JTS servers, using Oauth keys.
  2. Create a project area association between  RTC and RELM
  3. Create a LQE Data Source for RELM server  for the new RTC instance.
  4. Create user ids and roles that can access the data on both JTS instances.
  5. Ensure there is a lqe_user license on the new RTC instance to work with the LQE indexer.
  6. Create the the Data Source for the TRS provider in Rational Engineering Lifecycle Manager (RELM) Query Engine.
  7. Use RELM to search, reuse and do impact analysis on your product lifecycle resources.

Here are some recent bumps I hit setting it up. I hope this can help others in case they hit the same issues which are being addressed.  There were two problems and two work arounds.

1.  Error WARN  com.telelogic.festival.generalservices.util.UriUtils  – [Message:Unable to convert to legacy format because the doors resource url <doors://>” DWA installation was failing because InfoCenter command example didn’t work in  dbadmin example below. The reason that the dbadmin fails silently when a copy and paste of the command was done was because some of the characters when copied and pasted do not end up as the right ASCII characters that the command expects for switches. For example, the double quote (“) character surrounding the dcnChannelName value ends up to be the wrong ASCII character when pasted and has to be replaced with a (“) character to make it work. It does not return an error message when the wrong character is encountered. .  Work around was to enter or type quotes in and one dbadmin command at a time.  

Image

2.  DOORS TRS Authentication using JTS OAuth was failing because DOORS TRS was returning mixed case in server token names back to LQE.  Work around was to create all data sources in RELM LQE for token and authorization URLS using lower case.

 

 

 

Posted in Uncategorized | Tagged | Leave a comment

I was recently asked what resources are available to help setup LDAP for CLM on WebSphere Application Server. Here are some jazz.net articles and infocenter help pages

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.base.doc%2Finfo%2Faes%2Fae%2Ftsec_was_ad.html
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_instl_config_ldap_on_was.html
http://jazz.net/library/article/549/
http://jazz.net/library/article/479
http://jazz.net/library/techtip/96

There is a workshop for Collaborative Lifecycle Management Administration Workshop
https://jazz.net/wiki/pub/Main/CLM2012AdminWorkshop/lab-workbook.pdf

Enjoy.
Carlos

Posted in Uncategorized | Leave a comment

Exporting from Rational DOORS and importing to Rational DOORS Next Generation by using ReqIF

I am pleased to announce the availability of a DOORS Next Gen Technical Article on Jazz.net https://jazz.net/library/article/1243 The article is titled “Exporting from Rational DOORS and importing to Rational DOORS Next Generation by using ReqIF” and is for users of IBM Rational DOORS 9.5 and later who want to adopt either IBM Rational DOORS Next Generation 4.0.1 and later or IBM Rational Requirements Composer 4.0.1 and later for selected new projects.

For certain projects, you might want to seed a Rational DOORS Next Generation or Rational Requirements Composer project with information from a Rational DOORS project. To do so, you can export modules from Rational DOORS to Rational DOORS Next Generation or Rational Requirements Composer by using Requirements Interchange Format (ReqIF).

Shiv Kumar Singh is a member of the SSE Jump Start Team, and leads the early adoption program for Rational DOORS Next Generation. The SSE Jump Start Team assists ISSR, CTPs, and IBM partners and customers with PoC and PoT related to SSE Solutions, including the Rational solution for Collaborative Lifecycle Management (CLM) products, Rational DOORS, Rational DOORS Next Generation and Rational Engineering Lifecycle Manager. Prior to this role, he helped several IBM customers adopt many SDLC processes and IBM Rational tools. He can be contacted at sksingh@us.ibm.com

Thanks,

Carlos Ferreira

Posted in DOORS, DOORSNext, Intermediate, Level, Rational Products | Leave a comment

What should be included in a software development kit?

I am working on a draft proposal for developing a SDK.  Would like to hear feedback on what you think is the minimum required to include in an SDK.

Required Pre-requisites

  • Specifications like OSLC, J2EE,  etc
  • Pre-requisite libraries like LYO (which includes open source like JAX-RS(Apache Wink)  etc)
  • Built and supported on OS platforms
  • Key supported integration Use Cases

API Documentation

  • Easily understood Object vocabulary
  • Tutorials for each use case
  • Sample code
  • Working sample application and implementation

Licensing

  • Terms and conditions
  • License key enforcement

Test Suite

  • Compliance verification tool or scenario.

Installation

  • Method for packaging and installing adapters
  • Installation guide ( How to configure OAuth, LQE, etc )
  • Installation verification test tool

Productivity Tools and Extensions

  • IDE / Eclipse views or perspectives to speed development

Also how does or should an SDK complement a community for:

  • Getting support
  • Offering a market place to market adapters or solutions build with the SDK
Posted in Intermediate | 3 Comments

Lessons learned adopting the IBM Systems and Software Engineering Solution

I recently had the opportunity to work on site with customers from all around the world on the Systems and Software Engineering (SSE) Solution Beta. I lead the SSE Jumpstart team, whose responsibility is to understand Systems customers business needs and help them adopt IBM’s new offerings. By working closely with early program customers, we identify where our solution does and does not meet their needs. This allows us to respond more quickly to improve the solution and capture lessons learned before the solution is generally available. Our mission is to make customers and partners successful using the SSE solution and iteratively improve the solution. The SSE Solution helps teams specify, design, implement and validate complex products and the software that powers them. It offers an integrated set of capabilities to enable you to predictably deliver competitive, high-quality products while meeting regulatory and compliance requirements. The Systems and Software Engineering (SSE) Solution includes:

  • IBM Rational DOORS for requirements management
  • IBM Rational Rhapsody and Rhapsody Design Manager for system and software modeling
  • IBM Rational Team Concert(RTC) for project, change, build and source management
  • IBM Rational Quality Manager (RQM) for quality and test management
  • IBM Rational Engineering Lifecycle Manager (RELM) to visualize, analyze and organize engineering data and their relationships
  • IBM Rational Solution Process Assets

The focus of the most recent beta was on IBM Rational Engineering Lifecycle Manager (RELM). This new offering was announced and blogged about by Meg Selfe, Vice President of Complex and Embedded Systems. The purpose of this technical article just published on Jazz.net  is to share some of the lessons learned while working with beta customers as they adopted the SSE Solution. The article answers some of the most common business and technical questions asked by the SSE beta customers. This information will hopefully be useful for solution architects and deployment specialists. The SSE solution adoption lessons learned are categorized into four areas:

  • Business Needs and Capabilities
  • Solution Architecture
  • Planning the Deployment and Installation
  • Using RELM

I hope you find the article useful when adopting the SSE Solution.

Carlos Ferreira
SSE Jumpstart Team

Posted in DOORS, Quality Manager, Rational Products, Rhapsody Design Manager, Systems and Software Engineering Solution, Team Concert | Leave a comment

Installing Rational Design Manager v4 on a Single JTS CRJZS0373E

I recently ran into an error installing Rational Design Manager v4 on the same JTS.  The error was “CRJZS0373E While contacting the identity server”   Since there weren’t any Google explanations beyond the single entry in the documentation I thought I would post the solution here.

How this error may happen.  When uninstalling and installing RDM.  If you happen to stop or not completely go through a JTS Setup when installing RDM.  RDM may think think you have completed the setup and turns on identity checks.

Troubleshoot

View conf/dm/teamserver.properties.  Look for:

com.ibm.team.repository.ws.allow.identity.assertion=false

Use Bare Tail DMO logs Jts40/server/logs/dm.log

How To Avoid This Situation and Solution

Ensure you do a clean install by removing old RDM or RELM

  1. Unregister RELM or RDM application from the JTS container.
  2. Stop JTS Server.
  3. Run Installation Manager to uninstall RDM or RELM
  4. Clean directories
  • Clean directories/jts40/server/conf  (if you are using Derby it would be in here.)

Remove rdm lqe relm sparql and vvc from this directory ( warning you will lose all your data)

  • Clean directory JTS40/server/tomcat/work/Catalina/amrrtcserver/ I deleted the folders “dm” and “vvc”. These can safely be deleted because they are recreated from the unzipped data in the tomcat/webapps directory when the tomcat server starts.
  • Clean directories/jts40/server/tomcat/webapps

Remove rdm lqe relm sparql and vvc from this directory

  • Clean directories /jts40/server/tomcat/work/Catalina/yourrservername/

Remove rdm lqe relm sparql and vvc from this directory.  Don’t remove LQE if other products are using it.

  1. If you are using DB2 you want to also should make sure you have dropped the tables used by RDM. In this situation we were using Derby so removing the /jts40/server/conf/rdm  directory would have also removed the derby db.
  2. Reinstall RDM( will include VVC)
  3. Including re-running JTS Setup.
  4. Reinstall RELM ( uncheck VVC option)

If you just deleted the DM plug-ins from the tomcat server, you could force the provision of the DM plug-ins again (that reside in server/conf/dm/sites). This was done by entering the URL https://amrrtcserver:9444/dm/provision. This provisioning is normally done once in one of the DM finalization steps during setup.

Posted in Rhapsody Design Manager | Leave a comment

Trouble Shooting Authentication using IBM Lotus Connections v3.0

Trouble Shooting Authentication using Lotus Connections v3.0

A great way to increase innovation is through knowledge sharing.   Three products that I use every day are Rational Team Concert, Rational Asset Manager and Lotus Connections.  These products provide Change Management, Asset Management and Collaboration capabilities which are important for being able to innovate successfully with a team.   I am investigating new ways of using and integrating these products.  So recently I tried to install Lotus Connections to learn more.    After completing my installation process for IBM Lotus Connections I hit a problem where I was unable to login.  Each time I tried I was redirected me back to the login page after it successfully accepted my credentials.

Logging in to WAS I could see that LDAP was enabled with WAS. I could see the users in LDAP there.  Going to the profile directory I could see I successfully populated the profiles database with my ldap users.  The issue had to be with the authentication.  I wanted to share the method below that ultimately allowed me to trouble shoot and solve the problem.  I hit many other problems but those were well documented on the Web.  This one however wasn’t and I think it maybe useful for others who are deploying notes or just plain WebSphere applications.

 Troubleshooting Security Problems in WebSphere

  1.  Enable Tracing – Turn on tracing to get the right level of logging to trouble shoot.   In the Integrated Solutions Console to go Troubleshooting logs and trace.

i.      Select your server in my case it was connections _server1

ii.      Select Diagnostic Trace

iii.      Configuration

iv.      In the components field replace  *=info with

*=info:com.ibm.ws.security.*=all:com.ibm.websphere.wim.*=all:

com.ibm.wsspi.wim.*=all:com.ibm.ws.wim.*=all

orig  *=info

2.       Confirm that you have global security / Single Sign On SSO

    1. a.      General Properties  Enabled
    2. b.      Required SSL unselected
    3. c.       Domain name with a leading period.  Mine was .funbox2.com
    4. d.      Enable Interoperability Mode and Web inbound Securty
    5. 3.       Confirm that you have federated repositories for Global Security
      1. a.      Confirm that  you have both defaultWIFIleBasedRealm and  LDAP RELM
      2. b.      Confirm your Repository Identifier  is setup with your directory server, host and port
      3. c.       Binding DN pointing to cn=root and  bind password  for LDAP root
      4. d.      Ensure LoginProperties is set to uid
      5. e.       Certificate Mapping to EXACT_DN
      6. 4.       Restart your Connections Server
      7. 5.       Use baretail.exe to trace the SystemOut.log file C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\logs\connections_server1
      8. 6.       Use baretail.exe to trace the trace.log file C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\logs\connections_server1

This showed the error “REALM doesn’t match”

The SystemOut.log file had this key error:

[2/17/12 7:58:02:265 PST] 0000004f J2EEContext   E   ASYN9999E: Unexpected Exception Occurred: com.ibm.websphere.asynchbeans.SerialDeserialException: Exception while deserializing a saved service.  Service=security. Unable to deserialize the Subjects in this Context, cause: the realms do not match

  1. 7.       At this point I shared the trace and logs with a friend who was familiar with these types of security errors.  He thought the error was likely caused by not having a three level url.   That included www.funbox2.com
  2. 8.       Since I was testing in a local sandbox I modified the hosts file C:\WINDOWS\system32\drivers\etc  I was missing the one with http://www.funbox2.com

127.0.0.1              localhost

127.0.0.1              funbox2.com

127.0.0.1              www.funbox2.com

  1. 9.       Updated the LotusConnections-config.xml so that it referred to hostname www.funbox2.com instead of funbox2.com for all occurrences of it.

C:\Program Files\IBM\WebSphere\AppServer1\profiles\AppSrv01\config\cells\funbox2Cell01\ \LotusConnections-config\LotusConnections-config.xml

  1. 10.   TO ensure the config changes get propogated across the WAS cluster / cell go back into the Integrated Solutions Console.  System Adminstration / Cell /  Nodes/ Select the node and do a Full Re-sychronize.

This solved my Lotus Connections Login problem and I can now use IBM Lotus Connections.    I now can claim I have successfully installed IBM Lotus Connections.

Posted in Lotus Connections, Uncategorized | Leave a comment