Workflow and ServiceDesk Community

I've done some searching around here and the Symantec KB, and WorkflowSWAT.com, but I'm not finding much (i.e.anything) about how to create software resources that can be used in an NS7 Software Management Solution.

Doing a little digging through the database and comparing against the SMP Console, I've been able to
- Create the Software Component resource,
- Create a detection (inventory) Rule resource,
- Create a software package resource,
- Create a software command line resource,
- Create an EXE software installation resource,
and have been able to associate the
- Software package to the Software Compnent,
- Software Program to Software Component
- Inventory Rule to Software Component,
- Command line to Software Package

BUT, in all of these, I've not been able to set anymore more than the name and description.  No where have I found that I can specify the *actual* command line, or the UNC to the package, and so on.

Although our Software repackaging lab is using Wise Package Studio, we manage the package metadata in an external database.  I need to be able to create Software Management Solution packages from this database, as well as a couple other external software creation / packaging processes in our environment.

Thanks,
Mitch

Hi Mitch

Have you find any way to specify the settings like command line and so on?
I'm in the same situation at the moment.

Thanks
Stephan

Looks like that will not be possible before SMP 7.0 SP5 and ASDK 7.0 will be released. Should happen soon, as the KB-Article is already there:

https://kb.altiris.com/display/1n/articleDirect/index.asp?aid=53165

Schnyders -- Nope, no solution.  Have investigated a number of possible routes (with Symantec Support) including direct SQL (no solution there) and the possibility of exporting an existing software resource to XML, modifying it, then importing the XML to create a new resource.  Doesn't seem like a very practical solution, but was headed to look into this until getting sidetracked on another project.

Looks like the new ASDK is going to finally be the answer.

Mistral -- Thanks for that update.

Has someone tried to use the new asdk? For me it generates only a new package but not entry in the software library so it's not usable. Any idee?

Yes, my colleague and I have both tested the new ASDK.  Unfortunately, it does not support Software Management Solution (i.e. NS7) objects.  Instead, it added NS6 object support to an NS7 server.  The documentation says it's to permit the migration of scripts from NS6 environments with minimal change. 

It seems to me it'd have been better to create an NS7-native ASDK and have people create scripts to leverage the new functionality in NS7, instead of perpetuating the NS6 architecture (in the NS7 environment).