Before using .NET components from BPM processes and objects, you must include them
into the project catalog. When you catalog a .NET assembly, you are gathering all the
necessary information that Studio needs in order to call and execute it at
runtime.
Before cataloging .NET components, ensure the Oracle BPM .NET
Bridge is running on the machine hosting the .NET assemblies.
Also ensure that you have created a module where you want to catalog the .NET
components. See Creating a Module.
To catalog .NET components:
-
Right-click on the module where you want to catalog the components.
-
Select
-
Select one of the following options:
| Option |
Description |
|---|
| Use existing configuration |
Select this option if you have already configured an External Resource
for Microsoft .NET Service. |
| Create a new configuration |
Select this option if you need to configure a new External Resource
for Microsoft .NET Service. See Creating an External Resource. |
-
Click Next.
Oracle BPM Studio connects to the .NET Bridge and presents you with a
file system browser of the host running the .NET Bridge.
-
Select the .NET assembly file containing the components you want to catalog.
Browse and select the .dll file that corresponds to the .NET assembly you
want to inspect, and click Next. Not every .dll file is
.NET file. If you have selected an invalid .dll file, an error is displayed. Click
Back to select the .NET .dll file again.
-
Click Finish to catalog the .NET components.
The components contained in the selected .NET assembly are now included in your
catalog.