Service Package form
Completing the Deployment tab

Use the Deployment tab of a service package to generate deployment files for a SOAP, .NET, EJB, Java, Portlet (JSR168), COM, or CORBA service package.

Before you begin

1. Create the service rules that belong to this service package. Then update the list on the Methods tab and save the form.
2. Make sure that your RuleSet list provides access to all the service rules in the package.
3. If your development team uses check-out and check-in, ensure that all service rules, service activities, and other rules they reference are checked in before using this tab. Rules in private RuleSets (that is, the checked-out versions of rules) are ignored when you click the  Generate Deployment Files   button.

Completing the fields

This section describes the fields on the Deployment tab. Complete this tab as appropriate for the service type.

Field	Description
Deployment Type	The options that appear in this field depend on what the Service Type is set to on the Methods tab. Type Description WSDL or WSDL for WebLogic. WSDL generates a WSDL file for SOAP or dotNET services. WSDL for WebLogic generates a WSDL file for SOAP services, using the appropriate syntax for WebLogic's WSDLtoJava tool. Use this option when the client application that communicates with these services is deployed in WebLogic. For information about building SOAP services, see Building SOAP Services, a document on the Integration section of the Pega Developer Network. V2.0(RMI) or V2.0(Local) Generates a JAR file that represents EJB service rules. For information about deploying EJB services, see Building EJB Services, a document on the Integration area of the Pega Developer Network. For information about the V2.0(SOAP) or V1.0(SOAP) options, see Building EJB Services, a document on the Integration area of the Pega Developer Network. RemoteJavaClass or LocalJavaClass For Service Java, to generate a JAR file that represents Java service rules. JSR168 Generates a portlet.war Web archive (WAR) file that represents a portlet service rule. For information about building portlet services, see Building Portlet Services, a document on the Integration area of the Pega Developer Network. WSRP 1.0 Producer Generates a portlet.war Web archive (WAR) file that can be deployed as an OASIS Web Services for Remote Portlets (WSRP) producer. For information, see PRKB-25032 How to deploy a Process Commander portlet as a WSRP producer. IDL To generate an OMG Interface Description Language file that represents CORBA service rules. See Deploying CORBA Services. (Deprecated) DLL To generate a (local Windows workstation) Dynamic Linked Library file that represents COM service rules. See Deploying COM Services.
Service Class	Specify the service class name (Customer Class Name) — the second key part the service rules (methods) in the package — to restrict the deployment file to represent only those service rules in that service class.
Generate Deployment Files	Save the service package. Then click this button to start the file generation. When Process Commander is finished, it stores the file in a top-level directory of the Process Commander application and displays the location of the file. You can then download the file.
Deployment Results	This text area describes the files created, and any errors encountered.

Deploying COM services

Use the Deployment tab to when working with Process Commander from a Windows 2000/XP client workstation that has Microsoft Visual Studio 5 or later installed. Use this tab only after completing and saving all the Service COM rules that collectively make up the package.

Click the button to generate an ActiveX DLL file that encapsulates selected sets of activities known as a package. For each activity in the package, the generated DLL has a public method that matches the activities name. Method arguments match activity parameters in quantity, order, and data type. The system creates a DLL with the following public properties exposed:

• sZeusServer — URL of an available Process Commander server
• sPortNumber — The TCP/IP port number dedicated to Process Commander HTTP requests
• sLoginName — Process Commander user name
• sLoginPassword — Process Commander user password

Process Commander places the generated DLL file on your client Windows workstation. You can build it with the downloaded ActiveX control named prPackageCOMint.

Deploying CORBA services

(Deprecated)) Use this tab to generate an Object Management Group IDL (Interface Definition Language) file. A client that wants to communicate with the Process Commander ORB (Object Request Broker) uses this IDL interface to construct client-side proxy objects to make the remote method calls.

The system places the IDL file in the idl folder of the Process Commander server. You can copy this text into your Windows clipboard and then paste it into a local text file, or the you can retrieve the file from the server.

To retrieve the generated IDL file, from the Process Commander server, start Internet Explorer and retrieve it from:

http://Process Commander server/idl/class name.idl.

Replace Process Commander server with the name of the Process Commander server node to which you connected. Replace class name with the Customer Class key part of the Service CORBA rule.

About Service Package data instances