B2B Integration 10.4 | Administering and Monitoring B2B Transactions | Service Development Help | Building Services from .NET Methods | Creating a .NET Service
 
Creating a .NET Service
You create a .NET service using the .NET service wizard. Using the wizard, you scan existing .NET assemblies to determine the methods they contain. You can then import the methods into Designer. Using the Designer .NET service editor, you can create .NET services that call those methods. For more information about the editor, see .NET Service Editor.
Before you can create a .NET service, make sure the .NET Common Language Runtime (CLR) is loaded (i.e., started). If it is not, use Integration Server Administrator to load it. For instructions, see webMethods Package for Microsoft .NET Installation and User's Guide .
You can invoke .NET services from flow services. You can also execute them from Designer. For more information, see Running a .NET Service in Designer .
* To create .NET services from a method
1. In the Service Development perspective, select File > New > .NET Service.
2. In the Create New .NET Service wizard, expand the IS package in which you want the new service(s) to reside and select the folder in which you want to create the service(s).
3. Click Next.
4. In the Assemblies for Auto Conversion panel, locate a .NET assembly on a drive where the CLR can access it.
This panel depicts the white-listed directories. The only files displayed in this dialog box are assembly DLLs or EXEs. You can select multiple .NET assemblies for importation.
5. After you have selected assemblies, click Next.
6. In the Select Specific .NET Services panel, select the methods you want to import into Designer. By default, all methods in all selected assemblies are selected. You can select or clear whole assemblies, whole classes, or individual methods as needed.
7. Click Finish. Designer creates a .NET service for each method and places it in the specified folder.
For assemblies that are not located in the same windows domain or on the same machine as the CLR, the CLR might fail to load an assembly and issue a security error if the assembly was compiled with the unsafe option or if user permissions for the remote directory do not permit access. To resolve either condition, copy the assembly to the machine where the CLR resides, set directory permissions appropriately, or configure a trust relationship between the domains.
You can view the variables for the resulting .NET service in the Input/Output tab. In addition to the variables supported by a specific method, there are standard variables that are part of each .NET service.

Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release