Windows Applications Component Types
Windows application component types consist of three types:
COM+ Application Component Type
A component of this type represents a COM+ application. COM+ applications are treated as a unit. The settings and content are installed as a group.
Browsing for a COM+ Application
When you browse for a COM+ application, the browser provides an alphabetical list of COM+ applications on the target system.
You can select a single COM+ application to be checked in. COM+ applications have no children and cannot be expanded.
Exported/Internal File Format
COM+ applications are exported into a Microsoft Windows Installer (MSI) file using the COM+ Admin SDK.
Component Differences
The COM+ Application is re-exported on the target system as an MSI file and compared against the MSI file used to install the application. The software will only indicate that there were differences, but will not indicate the details of the differences.
Installing a COM+ Application
-
If a COM+ application with the same name is already installed on the target system and running as a service, the existing application is stopped along with any running dependent services. The COM+ application will then be deleted from the COM+ catalog.
-
The new COM+ application is installed using the COM+ Admin SDK.
-
To start the COM+ application the user will have to use the startApp call step to manually start the COM+ application.
Uninstalling a COM+ Application
The COM+ application is uninstalled using the COM+ Admin SDK.
Error Conditions
Table 4–1 COM+ Application Error Conditions|
Action |
Condition |
Result |
|---|---|---|
|
Install |
COM+ Application already exists with the same name and either cannot be stopped or dependent services cannot be stopped. |
Installation fails |
|
Uninstall |
MSI file used for installation is no longer available |
Uninstallion fails |
|
Install or Uninstall |
Remote Agent does not have administrator privileges |
Installation or Uninstallation fails |
Extended Control Procedures
Table 4–2 COM+ Application Extended Control Procedures|
Name |
Parameters |
Description |
|---|---|---|
|
startApp |
appName – Full name of the COM+ application. |
Starts the COM+ application if it is run as a service |
|
stopApp |
appName – Fill name of the COM+ application to stop. |
Stops the COM+ application and all dependent services |
|
stopRouter |
N/A |
Stops the COM+ Routing services |
|
startRouter |
N/A |
Starts the COM+ Routing services |
|
installAsUser |
rsrcSrcPath – Name of the COM+ application rsrcInstallPath – Path to the *.msi file representing the application userID – User who is going to run the application password – Password of the user |
Enables installation of a COM+ application that runs as a particular user |
COM Component Component Type
This component type represents a COM file.
Browsing
To choose a file for this component type, select a *.ocx or *.dll file from the file browser.
Component Differences
The COM component is compared as a binary file against the file used during installation. The software indicates when there are differences, but does not provide details about the differences.
Installing a COM Component
The Regsvr32 utility is called to register the COM components in the DLL using the following command line:
regsvr32.exe /s file path |
Uninstalling a COM Component
The Regsvr32 utility is called to unregister the COM components in the DLL using the following command line:
regsvr32.exe /s /u <file path> |
After the DLL is unregistered, it is removed from the target system.
Error Conditions
Table 4–3 COM Component Error Conditions|
Action |
Condition |
Result |
|---|---|---|
|
Install |
The supplied .dll or .ocx file does not contain COM components |
Installation fails |
|
Uninstall |
The supplied .dll or .ocx file does not contain COM components |
Uninstallation fails |
Microsoft Windows Installer File (*.msi) Component Type
A component of this component type includes a silent Microsoft Installer (MSI) file.
Browsing
To choose a file for this component type, select a *.msi file from the file browser.
Installing an MSI File
The Microsoft Windows installer service is called on the MSI file to import it into the target system with the following command:
misexec /qn /i file path |
Uninstalling an MSI File
The Microsoft Windows installer service uninstall is called on the MSI file used during installation to uninstall the package using the following command:
msiexec /qn /x file path |
After msiexec finishes, the MSI file is removed.
Error Conditions
Table 4–4 Microsoft Windows Installer File Error Conditions|
Action |
Condition |
Result |
|---|---|---|
|
Install |
The supplied *.msi file is not a proper Microsoft Windows installer file. |
Installation fails. |
|
Install |
The agent does not have proper permissions to run installations |
Installation fails. |
|
Uninstall |
The package has already been uninstalled |
Uninstall fails |
- © 2010, Oracle Corporation and/or its affiliates