Software Deployment

You will want to use the System Search feature, and populate 2 properties with the registry values unique to versions 9 and 10.

registry values unique to versions 9 and 10.

Here is what I have done: created 2 features OracleODBC_9 and OracleODBC_10. Now, I went to ODBC and selected that feature (Eg. In the OracleODBC_9 feature - I created an ODC entry corresponding to Oracle 9 driver. Then I installed Oracle 10 on the machine, and created a ODBC entry and then opened my wsi and for the feature OracleODBC_10, I imported the ODBC entry corresponding to Oracle 10.

Question - Do I need to build a query in my features? Like right now, I have just added those features. Is wise smart enough to detect the Oracle driver on the machine and create the corresponding ODBC config?

Thanks

ORIGINAL: aek

registry values unique to versions 9 and 10.

Question - Do I need to build a query in my features? Like right now, I have just added those features. Is wise smart enough to detect the Oracle driver on the machine and create the corresponding ODBC config?



No, the System Search is itself the query which returns a value to a property. You would build conditions into the components containing the Oracle 9 and 10 ODBC configurations.

Look up conditional syntax in your msi.chm file

I'd make two points:

- Since ODBC junk ends up in the registry, set up your DSN after you've installed whatever flavour of Oracle you need, then export the relevant registry entries to .REG files. Finally, import those .REGs into your WPS project. See also the discussion 'ODBC error 1918'.
- Use SystemSearch along with LaunchCondition.
Note that the default WPS set-up has the LaunchCondition sequenced BEFORE SystemSearch, as sub-optimal an arrangement as is possible to imagine, so alter your WPS template so that SS comes before LC.
For your SS, decide whether you'll detect file, folder or registry entry to determine whether the requisite Oracle flavour is installed and then use the property's content as your LC.