SM 7 release?

[glg]

I'm finding all kinds of conflicting information. Saw a mention of official release at next week's conference, but soft release with dates last week or this week (unlikely to be any later this week due to US Thanksgiving holiday). Nothing on "old" website or new Software Update Manager site (which now has SC 6.2).

Anyone hear anything?

[tommy]

SM7 will be launched in Barcelona at the software convention so I expect it to be available for download shortly there after. (Some partners have had it for beta for a while and earlier this week it was released to all partners).

[daurkin]

I'm waiting to hear if it's been release to the US yet? Let us know.

[kobear]

FYI - HP has told us that SM7 is intended for the legacy HP ServiceDesk customers that will need to make the transition to the SC architecture. It is NOT intended for users of SC 6.x.

They will be following up later in the year with a SM7.1 release, which will be the release intended for SC customers.

Another highlight from that conversation: As of SM7, P4 is going away. The only option is a RDBMS.

[tommy]

Another highlight from that conversation: As of SM7, P4 is going away. The only option is a RDBMS.

Yep that is true. Only 3 options from now on: MS SQL, DB2 or Oracle.

[benvargas]

Has anyone installed SM7 using the SQL Server 2005 Express database bundled with the installation CD? I attempted to execute the batch file which is supposed to automatically install and create the database, but on every command in the batch file I see "Access is Denied."

I ended up opting to just manually install SQL Server 2005 Express and then ran though the SM7 installation and I got a sandbox system up and running fine. Just wondering if anyone else saw the same issue when using the batch file...

I tried it on Windows 2003 Enterprise R2 as well as Windows XP Pro SP2. I was thinking that it had something to do with DEP (http://support.microsoft.com/kb/875352) but disabling it didn't appear to resolve the issue. It must be an OS security setting somewhere preventing cmd.exe from executing those commands - but where?!?!

[tommy]

Has anyone installed SM7 using the SQL Server 2005 Express database bundled with the installation CD? I attempted to execute the batch file which is supposed to automatically install and create the database, but on every command in the batch file I see "Access is Denied."

I got the same error and found out it is because it is run off the dvd. Copy the folder to your hd and run it then you don't get the error.

And remember the ODBC driver needs to be installed first. SC uses ODBC to connect to MS SQL (DB2 and Oracle connections are native). I made that mistake and need to start over when I get a chance.

[benvargas]

I got the same error and found out it is because it is run off the dvd. Copy the folder to your hd and run it then you don't get the error.

And remember the ODBC driver needs to be installed first. SC uses ODBC to connect to MS SQL (DB2 and Oracle connections are native). I made that mistake and need to start over when I get a chance.

Ahh... I didn't think about trying to move it off the DVD, especially since their autotrun puts you in that directory! I ended up installing in the following order:

01. Downloading latest SQL Server 2005 Express (the one that came on the DVD didn't seem to install cleanly on Windows Server 2003, but it did install on Windows XP... downloading the latest version from Microsoft worked fine in Windows 2003).

02. Setting up ODBC.

03. Installed Server, Installed Client.

Of course, I did two server installations because I thought it failed since no 'server shortcuts' were created during install. I then saw in the help server that they're no longer advising that you can start/stop from a console (command line and services only in Win) so I guess they've done away with the automatic creation of the Server shortcuts.

Thanks again for the info Tommy - that one was driving me crazy!

[KevinH]

Ok, so SM 7 doesn't use P4 at all? SM 7 does away with the P4 to RDBMS mapping stuff entirely? So there is no DATA directory containing the P4 files? Anyone confirm this?

We are using SC 6.2.2 on SQL Server. Even though the entire P4 database is mapped to SQL Server the system won't start without the P4 Windows files and it must have exactly it's own P4 Win files, even though dbdict thinks there are zero P4 files (the table-like things) not in SQL Server. This is quite a kluge so getting rid of this will be nice.

But we had heard SM 7 would still have it's own DB (what I mentioned above) separate from the UCMDB (Universal CMDB), and it needed both. The UCMDB would be a central repository of data including that from other software tools. You people that have installed SM 7, did you have to also install the UCMDB? I gather the UCMDB is something coming from the Mercury product set.

Thanks...

[outlance]

Ok, so SM 7 doesn't use P4 at all? SM 7 does away with the P4 to RDBMS mapping stuff entirely? So there is no DATA directory containing the P4 files? Anyone confirm this?

There is a DATA directory that contains .unl files of all dbdicts that are used during installation to map out to the SQL database. The P4 files in DATA directory are removed.

You people that have installed SM 7, did you have to also install the UCMDB?

UCMDB is optional. There is no description coming with SM7 that describes how to integrate it. SM 7 is some kind of SC6.5 - they removed P4 and added some nice user handling features like new Search functionality, Templates, etc. from HP Service Desk.

HTH,

Lars

[tommy]

Ok, so SM 7 doesn't use P4 at all? SM 7 does away with the P4 to RDBMS mapping stuff entirely? So there is no DATA directory containing the P4 files? Anyone confirm this?

We are using SC 6.2.2 on SQL Server. Even though the entire P4 database is mapped to SQL Server the system won't start without the P4 Windows files and it must have exactly it's own P4 Win files, even though dbdict thinks there are zero P4 files (the table-like things) not in SQL Server. This is quite a kluge so getting rid of this will be nice.

You can start SC 6.x without the P4 files. You need to add the paramater that tells sc not to look for the files. The value for the parameter is the database TYPE not the database name. I have posted the parameter before. I can't remember it right now.

EDIT: How to run SC 6.1.x without P4 files when pushed to RDBMS

[KevinH]

Thanks for the info. I put in param "sqldictionary:sqlserver" and SC starts without the scdb files. I was concerned about what happens when you pull a file back to P4 to change the dbdict, eg I had to extend a field from varchar(1900) to varchar(5000) in SQL server. Which incidentally doesn't work in 6.2.2, err in the RDBMS mapping editor, fixed in 6.2.4. Anyway, when I pulled cm3r back to P4 it created 4 scdb files. Then when I put cm3r back in SQL Server I restarted and then could delete those new scdb files, all was fine. This elimination of the P4 files was pretty important because it streamlines the potential recovery process. Thanks again.

[sigtb02]

Any performance issues regarding pushing out all tables to an oracle SGBD. We are using SC 6.2.5 on a Windows 2003 server.