| Re: [osee-dev] Retirement of HRID |
Don This is Bob Bryant and I am still trying to get OSEE to install at home. I spent a lot of last week trying to get OSEE to install at home on windows 7 64-bit. I have found install guides on the web with varying instruction on starting the database, server, and application. 1. I installed eclipse 4.3 2. Added eclipse-SDK-4.3-win32-x86_64.zip 3. Executed step 1.8 at http://wiki.eclipse.org/OSEE/Users_Guide/Getting_Started#Installation_and_Initialization 4. Down loaded Postgres and installed with Password set to postgres and port set to 5432 5. Completed all the steps at http://www.eclipse.org/osee/documentation/installation/postgresql_install.php to setup the database. 6. Executed the Executed C:\Program Files\PostgreSQL\9.3>pg_env.bat 7. Executed C:\Program Files\PostgreSQL\9.3>pg_env.bat 8. I have started the application server using the runDemo.bat and: java -Dorg.osgi.service.http.port=8089 -Dosee.check.tag.queue.on.startup=true -Dosee.db.connection.id=postgresqlLocalhost -jar plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar –console 9. I have started OSEE by double clicking on the icon and using: eclipse -vmargs -Xmx512m -Dosee.log.default=INFO -Dosee.arbitration.server=http://localhost:8089 -Dosee.authentication.protocol=trustAll OSEE come up with:
When I try to add the ATS Perspective I get:
I have found other people on the web have had the same problem but I have not found a solution. What am I doing wrong? Bob Bryant Home Phone: 480.990.3632 Cell Phone: 602.430.2024 Email Address: bob.bryant@xxxxxxxxx From: osee-dev-bounces@xxxxxxxxxxx [mailto:osee-dev-bounces@xxxxxxxxxxx] On Behalf Of Dunne, Donald G The 5 character HRID (eg:SQ5DG) was created on every artifact in the database as an easier way to identify artifacts than using the 20 character guid (eg:AEG7ShVZIFb5pQo5TwgA). This extra id and the efforts to keep it unique caused un-necessary performance issues, extra database indexes and database storage. It was determined that this ID was un-necessary for all but existing ATS actions. The code change to make this switch was released as part of 0.14.0. If the ATS HRID is desired for legacy actions, tasks, goals and reviews, there is a BLAM that will populate the “ats.ATS ID” attribute with the HRID. Otherwise, another conversion will need to be provided to populate the existing actions with their Id. The code to generate HRIDs for all artifacts was removed in 0.14. The code to generate HRIDs for ATS objects will be removed in 0.15. Don |
