Multiple WSTDeployer configurations inside one Rhapsody project
Multiple WSTDeployer configurations inside one Rhapsody project
26.08.2008 12:44
Is it possible to have more than one Deployer configuration (specific to each TargetComponent) inside one Rhapsody Model?
I will have two TargetComponents with a different scope for the Model. The project will generate code for two products which differ only slightly. But each product will have it's one IDE project file.
Now each component shall generate code and deploy to the specific IDE project file. Is this possible?
Further on ... does the deployer support different configurations (Debug/Release) to deploy to the specific IDE configuration (Debug/Release)?
If both things are not possible, what would be workaround?
Michael
Re: Multiple WSTDeployer configurations inside one Rhapsody project
26.08.2008 14:46
Hi Michael,
Yes, it is possible to have different deployer configurations for each component in a Rhapsody model.
The IDE project file, which should differ, is specified by the path and filename. The project filename (e.g. GettingStarted.uv2) is set via component's tag. The path to the IDE project is specified by the WSTDeployer configuration dialog and stored in the local registry, because paths may differ from one PC to another.
The registry value of the Deployer configuration for one component will not conflict or override the value for other components in the same model. The registry key is saved depending on the following active elements:
- root title (read from the tag of the active component)
- current project
- active component name
- selected environment in the active configuration (e.g. BeethovenDev)
So if only one element differs, it is possible to store different WSTDeployer configurations side-by-side.
As the list above shows, different settings per configuration are only supported if the selected environments differ.
Restriction:
Enhanced WSTDeployer configuration for very specific modifications are available in the WSTDeployer.properties file. The properties specified in that file are always global for one product. It is not possible to store them component dependent or so.
I hope this answers your question.
Best regards, Eike
Re: Multiple WSTDeployer configurations inside one Rhapsody project
26.08.2008 16:01
Hi Eike,
I think you answered my question. As I can see from the "list", which is taken into account while storing deployer configuration, as long as the names of components differ, each component can have a specific deployer configuration.
With my second question I guess I had a misunderstanding on my side. I thought if I have two configurations e.g. Debug and Release for one component I still need two deployer configurations one for each configuration to specifiy where to put the files into the IDE project. Although Rhapsody will generate files for each configuration seperatly, these are still the "same" files and don't have to be deployed seperatly. I'm I right? Or did I miss something?
Best regards
Michael
Re: Multiple WSTDeployer configurations inside one Rhapsody project
26.08.2008 16:13
Hi Michael,
Yes, you are right. The same set of files will be generated in another subdirectory by Rhapsody, but the deployer will copy the to the same destination (IDE) directory. If relevant properties differ between your configurations, the generated file contents may differ slightly. In that case the last deployed configuration "wins".
Best regards, Eike