SOPERA Blog

SOPERA’s How-To Series

Sometime ago in SOPERA we decided that it might help our users if we were to produce a couple of “How-Tos” in which we would list tips, tricks, or describe the ways in which you can use various SOPERA product components effectively and quickly.

SOPERA’s code generator is currently designed to work only on Microsoft Windows Operating Systems. In this How-To, we’re going to show you how to run the SOPERA code generator in Linux.

Running the SOPERA Code Generator in Linux

To run the SOPERA code generator on Linux:

1. Zip the contents of the /ServiceStudio folder into a zip file.
2. Copy this servicestudio.zip file to you linux user home path (for example, in /home/soadev).
3. Extract the archive file to a directory (for example, into /opt/SOPERA/ServiceStudio).
4. Translate the cmd files set-env.cmd, build.cmd and codegen.cmd to a Linux sh file. Don’t forget to enable the execution of these sh files. They can be found in the folders: ServiceStudio/CodeGenerator , ServiceStudio/CodeGenerator/bin.
5. Create a soft link in the ServiceStudio/CodeGenerator folder:
   ln –s JeeWiz/resources/any/control JeeWiz\\resources\\any\\control
6. Enable the bash scripts’ ant file and and run to execute. The folder can be found in ServiceStudio/CodeGenerator/JeeWiz/external/ant1.7.0/bin.
7. Add a slash in line 36 of the includeSpec.vm file:
   Old: #set( $basicName="file:/${aSchema.xsdTargetFile}"
New: #set( $basicName="file://${aSchema.xsdTargetFile}"


   You can find the file in this folderServiceStudio/CodeGenerator/JeeWiz/SBBresources/SBBservice/control/schema.

8. Now, test your code generator!

Robert Lalyko Development Code Generator, Linux OS, SOPERA Code Generator

We have decided to publish a number of short, easy to follow, “How Tos” in our blog. Here is a short “how to” from our team related to Intalio and P2P.

Peer to Peer (P2P) Communication with Intalio 6.0.013

SOPERA BPM 2.0 allows the deactivation of process to process (peer to peer) communication. This feature is required for the implementation of the dual usage (invoke and provide) of one WSDL in BPM processes. This section describes how to do just that.

Disabling P2P Communication

To disable the P2P communication:

1. Add the attribute usePeer2Peer in the project deploy.xml file.
2. Set this attribute value to false in the project deploy.xml file for the specific partner link

Take a look at this example:


<dd:invoke partnerLink="..." usePeer2Peer="false">;
<dd:service name="..." port="..."/>
</dd:invoke>


That’s all!

Robert Lalyko Development