Vishal Modi


  Home  |   Contact  |   Syndication    |   Login
  45 Posts | 0 Stories | 95 Comments | 0 Trackbacks


Tag Cloud

Article Categories


Post Categories




Monday, October 17, 2016 #



  • Centralized queuing.

  • Decentralized queuing.

  • Multiplatform (Linux, Windows, Mac, etc)

  • Windows only

  • Standard based (AMQP)

  • No standard


Centralized vs Decentralized:

  • A message broker like RabbitMQ is a centralized message broker where messages are stored on a central or a clustered server and client/subscriber does pubsub from this central server.
  • MSMQ is decentralized and each machine has its own queue. Client can send messages to a particular queue and the subscriber can retrieve the message from that particular queue.

Multiplatform vs Windows only:

  • RabbitMQ is multiplatform message broker so clients from any platform can read/write messages to/from RabbitMQ. It also has client libraries written in .NET, Java, Erlang, Ruby, Python etc. Integration is easy.
  • MSMQ is a windows machine only messaging system.

Standards vs No Standards:

  • RabbitMQ follows one of the standard called AMQP (Advanced Messaging Queuing Protocol). If you have multiple platform taking with each other than RabbitMQ is a better option.
  • MSMQ uses its own proprietary messaging format. If you have a use case of windows machine talking with windows machine than MSMQ can suffice that use case. 

Tuesday, April 23, 2013 #

If you get the above error while connecting to Team Explorer from either Visual Studio 2008, the reason “might be” Microsoft Communicator or Live Messenger installed on the machine and on top of it if you also have Team Foundation Server Power Tools installed. I have seen this error so far only with VS 2008 with TFS 2010.

Somehow the Power Tools –> Team Members feature is trying to collaborate with the Microsoft Communicator members and throws below error as it might be failing to connect.


Quick Fix:

Go to Visual Studio 2008 –> Tools –> Options –> Team Foundation Server Power Tools and set Team Members flag as False. Restart Visual Studio and you should not get that error.



Vishal Modi


Monday, December 10, 2012 #

Out of the box, Team Foundation Server 2010 Build does not support building of setup projects (.vdproj). Although, you can modify the DefaultTemplate.xaml or create your own in order to achieve this. I had to try bunch of different blog post's and finally got it working with a mixture of all those posts.

Since you don’t have to go through this pain again, I have uploaded the Template which you can use right away :!310

  • Download and CheckIn this template into your source control. Modify your Build Definition to use this template. Unless you have CheckedIn the template, it wont show up in the template selection section in the process task of build definition.


  • In your Visual Studio Solution Configuration Manager, make sure you specify to build the setup project also.


  • You will get this warning in you build : “The project file “*.vdproj” is not support by MSBuild and cannot be build.

Hope it helps.


Vishal Modi

Reference blog posts I had used:

Thursday, November 29, 2012 #

Hi there,

Recently I was working with BizTalk Deployment Framework v5.0 for my BizTalk Sever 2009 projects and TFS 2010 Builds. I had followed all the steps mentioned in the BTDF documentation to create the build definition and also followed the steps to setup the Build Server with BTDF. After few hiccups I was stuck at this light.exe validation error. The detailed error is as below:

light.exe : error LGHT0217: Error executing ICE action 'ICE06'. The most common cause of this kind of ICE failure is an incorrectly registered scripting engine. See for details and how to solve this problem. The following string format was not expected by the external UI message logger: "The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance."

I found few blog posts and forum answers out there which had steps to resolve the error but all of them mentioned different things. Like:

  • Some mentioned that disable the validation itself so that the VBScript would not be called. (I didn’t want to disable the validation.)
  • Another said to put NT AUTHORITY\NETWORK SERVICE in the local Administrators group but this is not recommended as it opens up network security holes.

But what actually worked for me was:

TFS Build Service Account was part of the Administrator group on the Build Server which is OK. But somehow it was also part of the IIS_IUSR Group. I removed the TFS Build Service Account from the IIS_IUSR group. Queued up my TFS Build but same error. Again after some digging, I found that I had not restarted the Visual Studio Team Build Service.

In a Nutshell:

  • Remove TFS Build Service Account from IIS_IUSR Group.
  • Restart the Visual Studio Team Build Service, either from Services or TFS Console.




Hope this resolves the issue for someone and not waste bunch of hours.



Vishal Modi

Friday, November 9, 2012 #


Microsoft finally released the Team Foundation Service in late October 2012 after its long time in the preview phase. I was already using the TFS Preview which was free but I was happy to see Microsoft releasing the Team Foundation Service also FREE for upto 5 users. Isn't that great news? I know there are bunch of other free source control repositories (Github, Bitbucket, SVN etc.) out there but I somehow like TFS better. Also the other good thing about the final release was that I didn’t had to do any kind of migration of my code from preview to final release version. Just changed the TFS connection URL and it worked like a charm.

Anyways, if you are a startup with small team and need some awesome Source Control along with all the good Project Management, Continuous Integration (Build, Test, Deploy), Team Collaboration, Agile/Scrum planning etc. features than Team Foundation Service is your answer. Microsoft has not yet released their pricing for more than 5 users and will be releasing it sometime in early 2013. What if as of now you have a team more than 5 users and you want to use Team Foundation Service, the good news is you can use it for FREE but when they release the final pricing, you will have to transition to the paid plan.

Lot of story, getting to the point, connecting to Team Foundation Service with Visual Studio 2012 is straight forward and would work out of the box but it wont for previous versions of Visual Studio. You will have to upgrade to the latest service pack first and than install the forward compatibility pack. (1st : Service Packs & 2nd: Forward Compatibility packs)

For Visual Studio 2010:





3  4


For Visual Studio 2008:

Visual Studio 2008 will not work if you only put You will have to put your collection name too as shown below.








By the way, it doesn’t matter if you are an Apple Application Developer or Android App Developer, you can still use Team Foundation Service as your source control. Below are few links to connect to Team Foundation Service with other IDEs:

Happy coding.

Vishal Modi

Wednesday, November 7, 2012 #

Hello BizTalkers,

Finally, Microsoft released the beta version of BizTalk Server 2010 R2 and now its called BizTalk Server 2013. I had tried the BTS 2010 R2 CTP version on Windows Azure VM and particularly I was excited about the RESTful services support and ESB fully integrated into BizTalk. Well didn’t get chance to test it much, Azure & VM running cost associated Winking smile. Anyways, I was waiting for this announcement and I was so much glad that Microsoft finally released the on premise one.  Check what’s new in the BizTalk Server 2013.  Officially Microsoft says that BizTalk Server 2013 “beta” is not supported on Windows 8 but I was curious to try it out. Below is my installation and configuration experience.

Virtual Machine configuration:

  • VM Ware Workstation 9.0.
  • Windows 8 Enterprise x64.
  • SQL Server 2012.
  • Visual Studio 2012 Ultimate.
  • BizTalk Server 2013 beta.
  • Windows 8 Machine name: WIN8
  • Local Administrator account name: Admin

First I installed Windows 8 Enterprise on a VM Ware Workstation 9.0 and updated the OS. Even Windows 8 is the new release so luckily didn’t had much updates to perform.

Next Installed Visual Studio 2012 Ultimate which was straightforward installation.

Next Installed SQL Server 2012. Select New SQL Server stand-alone installation & followed the steps as shown in the screenshot below.





5 6














Once the installation is finished, fire up SQL Server Management Studio and try connecting. Initially when the management studio opened up, I thought why did Visual Studio 2010 open when I tried opening SQL Management studio but well, they made the interface alike VS 2010. Cool, I like it.


Next is the real deal, download the BizTalk Server 2013 and unzip to particular folder. Double click the Setup.exe and follow the steps in the screenshots.


Install Microsoft BizTalk Server 2013 beta.





I selected all the normal artifacts and also all the artifacts under Additional Software's.






So far so good. Next Launch BizTalk Server Configuration and I used Basic configuration as shown in screenshot below.




Didn’t expect to see this but “wala”. Successful in the first shot. Still I wasn’t sure & something would have gone wrong so fired up the BizTalk Server Administration Console and that too came up just fine.

Still was not able to believe so created a simple messaging application:  message in –> message out and that too worked just fine. Finally I was convinced that BizTalk Server 2013 did work on Windows 8.


Next step was to install the ESB Toolkit 2.2 which is now integrated with BizTalk Server and does not come as a separate standalone installation file. Again run the BizTalk Setup.exe from the unzipped folder.


Install Microsoft ESB Toolkit.





Next, unlike ESB Configuration would  not open up by itself so go to “Windows 8 so called Start” (I could not resist to write this) and open the ESB Toolkit Configuration wizard. Below screenshot display the configurations I used. Also you can find them on MSDN here.










Finally after the ESB Configuration, I open Admin Console and checked the 2 ESB application deployed. Cool. This concludes my experience about installation and configuration of BizTalk Server 2013 Beta & ESB Toolkit 2.2 on Windows 8.

I will try and keep writing about BizTalk Server 2013 and its use with RESTful Services etc.


Vishal Mody

Wednesday, September 5, 2012 #

Hello folks,

Recently I was involved in Installation and Configuration of Team Foundation Server 2010 Farm for a client. A month after the successful installation and configuration, Microsoft released Team Foundation Server 2012 in mid August 2012. Well, the company was using Borland Starteam as their source control and once started to use TFS 2010, their developers and project managers love it. No wonder right, moving from StartTeam to TFS. ;-) Anyways, long story short, they are now thinking of upgrading to the newest version of TFS. I had to work on what was supported and not supported by TFS 2012 from what we had currently in our Farm.

Below are some basic Hardware and Software requirements for TFS 2012:

Operating System:
  • Windows Server 2008 with SP2 (only 64bit)
  • Windows Server 2008 R2 with SP1 (only 64bit)
  • Windows Server 2012 (only 64bit)

SQL Server:

SharePoint Products:

Project Server:

Number of users




Hard disk

Fewer than 250 users

Single-server (Team Foundation Server and the Database Engine on the same server).

1 single core processor at 2.13 GHz

2 GB

1 disk at 7.2k rpm (125 GB)

250 to 500 users


1 dual core processor at 2.13 GHz

4 GB

1 disk at 10k rpm (300 GB)

500 to 2,200 users

Dual-server (Team Foundation Server and the Database Engine on different servers).

This row is for Team Foundation Server.

1 dual core Intel Xeon processor at 2.13 GHz

4 GB

1 disk at 7.2k rpm (500 GB)


This row is for the Database Engine with 500 to 2,200 users.

1 quad core Intel Xeon processor at 2.33 GHz

8 GB

SAS disk array at 10k rpm (2 TB)

2,200 to 3,600 users


This row is for Team Foundation Server.

1 quad core Intel Xeon processor at 2.13 GHz

8 GB

1 disk at 7.2k rpm (500 GB)


This row is for the Database Engine with 2,200 to 3,600 users.

2 quad core Intel Xeon processors at 2.33 GHz

16 GB

SAS disk array at 10k rpm (3 TB)

More information on TFS Upgrade Requirements can be found here. Hardware Recommendations can be found here.

Vishal Mody

Friday, April 6, 2012 #

Hello folks,

     Recently I got involved in a project for building a demo application for one of our customers with Kinect for Windows. Yes, something similar what Tom Cruise did in the movie Minority Report. Waving arms, moving stuff around, swipes, speech recognition, manipulating computer screens without even touching it. Pretty cool!!! The idea in the movie showed us how technology would be after 50 years from that day.


Minority Report Movie clip.


     Well, that 50 years of time frame got squeezed and recently on Feb 1st 2012, Microsoft released the official Kinect for Windows SDK. That’s just 10 years from the movie release. Although, the product is in it early stages but with developer creativity and continuously improving hardware, those features shown in the movie are not very far away from becoming a reality. Soon after releasing the SDK, Microsoft again announced in March the release of its new Kinect for Windows SDK version 1.5 which is coming out in sometime May. More history about Kinect.

Anyways, so for a newbie with Kinect, where would you start. Here is what I would suggest you can do.

I always hate developing UI application but well, you would need to get your hands dirty with WPF too in order to work with Kinect. So get started with WPF concepts too.

I will keep adding stuff to the list once I come across them but so far the above list would definitely get you started building your first Kinect apps.

Till then Happy Kinecting…!!!!! Winking smile


Vishal Mody 


Tuesday, February 21, 2012 #

In this post we will see few of the initial steps for developing BizTalk Solutions for integrating with PeopleSoft Enterprise Systems using PeopleSoft Adapter. In order to proceed further, you must have Installed and Configured PeopleSoft Adapter properly, both on BizTalk side and PeopleSoft System side. This particular post is based on PeopleSoft HRMS 9.0 system. But the steps shown below should be same for any PeopleSoft Enterprise System.

The steps will be same to connect to any Component Interface of PeopleSoft System. Here we will be connecting to the Employee Personal Data component interface.


BizTalk Server 2010

Visual Studio 2010

SQL Server 2008 with SP2

PeopleSoft HRMS 9.0 with PeopleTools 8.52


  • Open Visual Studio 2010 and create a new BizTalk Solution. In this case we named it as PSDemo.


  • Open BizTalk Server Administration Console and you can use any Application or you can create a new Application. Here we are using the BizTalk.EnterpriseApplication.


  • Go to Send Ports for this application and right click and create a new Static Solicit Response Send Port.


  • Name the send port appropriately and select PeopleSoft as the Transport Type and XML Transmit and XML Receive as the pipelines as shown in the screenshot.


  • Click Configure for the PeopleSoft Adapter and fill in the appropriate values for the PeopleSoft adapter properties. You can keep other values as default ones apart from the Application Server Path, Java_Home, Password, PeopleSoftJarFile and Username.


  • Click Apply –> Ok. Restart the BizTalk Host Instance and then Stat this particular Send Port. Check the event log if you have any errors after starting the Send Port.


  • Go back the the Visual Studio solution. Right click the project and click Add Generated Items.


  • Click Add Adapter Metadata.


  • From the list of registered adapters, select PeopleSoft Adapter and wait for a second and you will see the list of Send Ports registered with PeopleSoft Adapter. Select the one which we created above and click Next.


  • Wait for few seconds and you will see all the Component Interfaces for the PeopleSoft System. If you don’t see any CI then there might be some issue in your PeopleSoft Adapter configuration on the send port side. Check the Event Log for any error. For any JVM related errors, check out this blog post to fix them. It also discusses other error fixes.


  • Select the component interface from the list for which you want to generate the metadata for. Here we will be using CI_Personal_Data which is a component interface for PeopleSoft HRMS Employee Personal Data.


  • Once selected click Finish and after few seconds you will see the schemas and orchestration added for this CI.

 11     12


Tuesday, February 14, 2012 #

Commonly when you try to connect the Enterprise Applciatons with BizTalk Adapters you might get errors like :

E-PSFT0029: JVM was not started


Unable to find JAVA_HOME.

As the error says, it is unable to locate the JVM.dll and unable to start it.


  • Make sure the folder having JVM is present as a value in PATH variable of environment variables. Say for PeopleSoft Applications, the JVM can be found with the app called JRockit so make sure the folder path of JRockit containing the JVM is properly present in the environment variable value.

Path Env Variable

  • Apart from PATH variable, make sure you also have a variable named CLASSPATH with the Jar file location in it. The mentioned below is a psjoa.jar file needed for PeopleSoft Adapter. 

ClassPath Env Variable

  • Download this exe and provide the path of the JVM.dll and check if its able to start it successfully. If yes then you can use this Folder path in the BizTalk Server Adapter configurations on the BizTalk Receive or Send Ports. If the JVM is unable to start with this tester then you know the problem is with this JVM.dll. May be some kind of security settings or access issues. Get the JVM.dll working.





  • Make sure you have all the necessary access to the user which will be connecting to the Enterprise Application. Also for the user on which the BizTalk Host Instance, BizTalk Adapters, BizTalk Send Handlers, BizTalk Receive Handlers etc are running. For eg, for PeopleSoft Applications, you will have to configure the PeopleSoft System as shown in this post so that BizTalk Adapter can connect to it.
  • Lastly, make sure you have all the values in the BizTalk Send/Receive Port Adapter configurations properly with all the usernames, passwords, case sensitive values correctly.

Hope these helps.


Vishal Mody

Wednesday, January 25, 2012 #

Architecture of PeopleSoft Adapter:

The BizTalk PeopleSoft Adapter is based on the BizTalk Server Adapter Framework. More info: How the Adapter Is Designed: The Adapter Framework. The PeopleSoft adapter basically communicates with the PeopleSoft Component Interfaces via the PeopleSoft JOLT protocol (over TCP/IP). The adapter communicates with PeopleSoft system by receiving a XML message which is later encapsulated into a SOAP request using the PeopleSoft psjoa classes. With this connection we can get the metadata to call into the existing Component Interfaces and generate the API schemas and use them within BizTalk Server for mapping, orchestrations at design time and runtime. According to Microsoft, if you need to have PeopleSoft Enterprise to initiate the call to BizTalk Server, they recommend using the HTTP adapter. More info : Creating a PeopleSoft HTTP Host and Port

PS Adp 1

More detailed information on PeopleSoft Adapter Architecture can be found on MSDN.

Requirements for PeopleSoft Adapter:

  • BizTalk Server Enterprise Adapters installed and configured and of course BizTalk Server 2010 installed and configured.
  • Java Development Kit (JDK) 1.4.2 or later.
  • Access to the PeopleSoft Application Designer to deploy Component Interface. The PeopleSoft Application Designer does not have to be on the BizTalk server.

Installing BizTalk Server Enterprise Adapters:

  • Open the BizTalk Server 2010 setup and click Install Microsoft BizTalk Adapters.



    • Install Adapters packs for all the 4 Steps.








  • This concludes the installation the BizTalk Adapters for Enterprise Applications. Don’t worry about the warning in Step1.


Configuring PeopleSoft Adapter for BizTalk Server:

  • Open BizTalk Server Administration Console –> Platform Settings –> Adapters –> Right Click –> New –> Adapter


  • In the new window, choose name as PeopleSoft and from the adapter dropdown choose PeopleSoft Enterprise. Click Apply –> OK and restart your Host Instances. Now you can see the PeopleSoft Adapter as the installed BizTalk Adapters.



  • This concludes the configuration of PeopleSoft adapter on the BizTalk side. Next is to create a Component Interface on the PeopleSoft side though which BizTalk PeopleSoft adapter can communicate.

Configuring a New Component Interface for PeopleSoft:


- PeopleSoft PeopleTools 8.52

- PeopleSoft Enterprise HRMS 9.0

- Oracle Web Logic Server

- Tuxedo 10gR3

- JRockit JDK R28.1

Step1: Creating a New Component Interface:

  • Go to the Server where you have PeopleSoft Enterprise Application installed.
  • Go to Start –> All Programs –> PeopleSoft (can differ according to version you have installed) –> Application Designer. Log in with your PeopleSoft user ID.

PS Adp 2

  • On the File menu, click New. In the New dialog box, select Component Interface.

PS Adp 3

  • Click Select on the next window and it will show list of current CI. Select any Component Interface which does not have any keys. After you select the appropriate component, you see a message asking if you want the fields exposed in the selected component to become the default properties of the Component Interface.

PS Adp 4

PS Adp 5

  • Click Yes to confirm the Default Property Definitions or No if you don’t want any properties initially created.

PS Adp 6

  • On the File menu, click Save As. In File Name, enter GET_CI_INFO, and then click OK.

PS Adp 7

  • Right-click any method of your new Component Interfaces, and then click View PeopleCode. A new blank window will pop up.

PS Adp 8

  • Copy and paste the contents of <PeopleSoft installation directory>\PeopleSoft Enterprise\config\get_ci_info.pc into the window. Open the file in notepad and copy the contents of it.

PS Adp 10

PS Adp 9

  • On the File menu, click Save. You now have a new Component Interface.
  • Just to verify if you perfomed the steps correct. Close the Application Designer. Reopen Application Designer and Log in with your PeopleSoft user. Go to File –> Open –> Component Interface and browse to GET_CI_INFO and open it. You should see something similar as shown below.

PS Adp 11

Step2: Set the PeopleSoft Component Interface security:

In the below steps, the Permission lists, Roles and User Profile are just selected randomnly to display the steps. Please select the appropriate Permission List, Roles and User Profile according to your use and accessibility. Highly recommend setting up this security with a PeopleSoft Administrator person or a PeopleSoft expert.

  • Sign in to PeopleSoft Web Portal.


  • Select PeopleTools, Security, Permissions & Roles, Permission Lists.


  • Click Search, select the relevant Permission List, and click the appropriate list hyperlink. The Permission List pane opens on the right.


  • Click the right arrow next to the Sign-on Times tab to display the Component Interfaces tab. Click the Component Interfaces tab.


  • Click the + button to add a new row to the Component Interfaces list.


  • Select the GET_CI_INFO component interface and click Edit.



  • Click Full Access (All) to set the methods to Full Access. Click OK.


  • Scroll down to the bottom of the Component Interfaces window and click Save.


  • Select PeopleTools, Security, Permissions & Roles, Roles. Click Search, select the relevant Role and click the appropriate list hyperlink.


  • The Role pane opens on the right. Click the Permission List tab.

  • Click the + button to add a new row to the Permission List.

  • Select the GET_CI_INFO Permission List.

  • Scroll down to the bottom of the Roles window and click Save. [Save as GET_CI_ROLE]


  • Select PeopleTools, Security, User Profiles, User Profiles.

  • Click Add New Value, type BizTalk into the text box, and click Add to display the General tab


  • Select a Symbolic ID in the drop-down box.

  • Type a Password and Confirm Password.

  • Choose an appropriate Navigator Homepage.

  • Choose an appropriate Process Profile.

  • Choose an appropriate Primary Permission List for the Primary field.

  • Choose an appropriate Row Security Permission List for the Row Security field.


  • Click the Roles tab.

  • Click the + button to add a new row to the Roles list.

  • Select the GET_CI_INFO Role.

  • Select the PeopleSoft User Role.

  • Select the Standard Non-Page Permissions Role.

  • Scroll down to the bottom of the User Profile window and click Save.


Step3: Testing the Component Interface:

  • Start  PeopleSoft Application Designer. Click File, Open and select Definition = Component Interface.

  • Select GET_CI_INFO CI from the list of Component Interfaces.


  • After opening GET_CI_INFO, right-click anywhere in the right pane of your Component Interface definition and select Test Component Interface.

    The Component Interface Tester dialog box appears.


  • GET_CI_INFO should not contain any keys. If keys are present, you need to return to Application Designer and remove them.

This concludes the set up of the GET_CI_INFO Component Interface needed to communicate with BizTalk Server. Open-mouthed smile

In the next coming blog posts we will see how we can generate metadata with this GET_CI_INFO Component Interface.


Vishal Mody Winking smile

PS: Reference from MSDN article : Microsoft BizTalk Adapters for PeopleSoft


Tuesday, January 24, 2012 #

Step 9: Completing the Database Setup:

This step is a very critical step and should performed with very much attention. Below mentioned steps are the ones which I thought were required for the environment I was building but I very highly recommend that you perform this step from the Oracle Installation document which can be found here. Look at Chapter 7 in this document. 

Updating PeopleTools System Tables:

  • Here PS_HOME is the directory where you have installed your PeopleTools. In our case its C:\PT852 directory.
  • Got to PT852\scripts and run rel851u.sql and rel852u.sql sql scrips.
  • Edit and run the grant.sql script in the PS_HOME\scripts directory. This will grant permissions to the CONNECTID. Run the script as a user with Microsoft SQL Server system administrator privileges.
  • Invoke Data Mover by running PS_HOME\bin\client\winx86\psdmt.exe. The PeopleSoft Logon window appears.Log on using a valid PeopleSoft Operator ID, such as PS for HRMS.
  • Run the storeddl.dms Data Mover script in the PS_HOME\scripts directory.
  • Invoke Data Mover by running PS_HOME\bin\client\winx86\psdmt.exe. The PeopleSoft Logon window appears. Log on using the ACCESSID you specified when you created your Data Mover scripts with the Database Setup program. This will start Data Mover in bootstrap mode.
  • Run the msgtlsupg.dms Data Mover script in the PS_HOME\scripts directory. This will update the PeopleSoft PeopleTools messages in your database.

Updating PeopleTools Database Objects

  • Launch Appplication Designer and sign on to your databse with a valid PeopleSoft UsedID.
  • Select Tools, Copy Project, From File.
  • In the resulting dialog box, change the import directory to PS_HOME\projects, select PPLTLS84CUR from the list of projects and click the Select button.


  • The Copy From File dialog box appears. Select all object types and then click the Copy button. When the progress window disappears, the project has been copied


Altering PeopleTools Tables:

  • Launch Application Designer with a valid PeopleSoft user ID and sign on to the installed database. Select File, Open. Select Project, enter PPLTLS84CUR in the name dialog box, and click OK.
  • Select Build, Project.


  • Select Create Tables and Alter Tables in the Build Options region.
  • Select Build script file in the Build Execute Options region.
  • Click Setting. The Build setting dialog box appears:




  • Click OK.The Build dialog box reappears. Click Build. Click Close when the process is completed.

Updating the PeopleTools System Data:

  • Invoke Data Mover by running PT852\bin\client\winx86\psdmt.exe. The peoplesoft logon window appears.
  • Log on with the AccessID and Password.
  • Run the DataMover scripts from the application database version. In our case run Pt851tls.dms and pt852tls.dms
  • Run the pslanguages.dms Data Mover script in the PS_HOME\scripts directory.
  • Run the tlsupgnoncomp.dms Data Mover script in the PS_HOME\scripts directory.
  • Open Data Mover using a valid PeopleSoft Operator ID, such as PS for HRMS
  • Run the msgtleng.dms Data Mover Script in the PS_HOME\scripts directory.
  • Run the ptstreng.dms Data Mover script in the PS_HOME\scripts directory.
  • Run the storept.dms Data Mover script in the PS_HOME\src\cbl\base directory.
  • Run the ptdefnsec.dms Data Mover script in the PS_HOME\scripts directory.
  • Run the createvw.dms Data Mover script in the PS_HOME\scripts directory.

This concludes post database configurations.

Step10: Configuring the Application Server on Windows:

  • Go to command prompt and go the the location C:\PT852\appserv
  • Type PSAdmin and click enter
  • Select 1 for Application Server and press enter.
  • Specit 2 to Create a domain and press enter.
  • Enter the domain name to create: say HR84
  • Specify 4 for small if this is your initial domain installation and press Enter.
  • After the system creates the domain, this prompt appears:
  • Would you like to configure this domain now? (y/n) [y] :

Enter y. The PeopleSoft Application Server Administration menu appears with a Quick-configure menu

similar to this:


Quick-configure menu -- domain: HR84


Features Settings

========== ==========

1) Pub/Sub Servers : No 15) DBNAME :[HR84]

2) Quick Server : No 16) DBTYPE :[MICROSFT]

3) Query Servers : No 17) UserId :[QEDMO]

4) Jolt : Yes 18) UserPswd :[QEDMO]

5) Jolt Relay : No 19) DomainID :[TESTSERV]

6) WSL : No 20) AddToPATH :[c:\Program FilesÞ

\Microsoft SQL Server\100\Tools\Binn]

7) PC Debugger : No 21) ConnectID :[people]

8) Event Notification : Yes 22) ConnectPswd :[peop1e]

9) MCF Servers : No 23) ServerName :[]

10) Perf Collator : No 24) WSL Port :[7000]

11) Analytic Servers : Yes 25) JSL Port :[9000]

12) Domains Gateway : No 26) JRAD Port :[9100]

13) Load config as shown

14) Custom configuration

h) Help for this menu

q) Return to previous menu

HINT: Enter 15 to edit DBNAME, then 13 to load

Enter selection (1-26, h, or q):

· Press 6 and Enter this is enable WSL

· Press 8 and Press Enter this will disable Event Notifications.

· Press 17 and type PS

· Press 18 and type PS

· Press 21 and Type PSCID ( This will be your connect ID)

· Press 22 and Type P@ssw0rd (This will be your connedID Password)

· Press 13 and this will Load the configuarations which we configured above.

  • In the next menu, select 1 to Boot this Domain
  • In the next menu, select 1 for Serial Boot and 2 for Parallel Boot. This will boot the domain which we created above.
  • Next we will be doing PIA installation so keep the App server up and running.
  • Check the screenshots for your references.





  • This concludes configuration of Application Server


Step11: Setting up the PeopleSoft Pure Internet Architecture(PIA):

  • Go to PS_HOME\setup\PsMpPIAInstall and run setup.bat.
  • Click Next on the Welcome to the Installation Wizard for PeopleSoft Internet Architecture window.
  • Next follow the instruction’s as shown in the screenshots below.














  • This will create a PIA domain. Next step is to start this Domain.
  • GO to Command Prompt and go to C:\PT852\appserv location
  • Type psadmin and Press Enter.
  • Specify 4 for Web PIA Server
  • Select 1 for Administer a domain.
  • Select the domain you want to administer by entering the appropriate number.
  • To start a web server domain, enter 1, Boot this domain.
  • The boot command invokes the startPIA.cmd script, and you see the progress and a status message on the console window.

Starting the domain..................

The domain has started.

Step12: Accessing the PeopleSoft Application:

PS Sign On

PS HomePage

This concludes the installation and configuration of PeopleSoft HRMS 9.0 Application.

Step6: Installing People Tools 8.52:

  • After you download and extract the PeopleSoft PeopleTools installation files you can find the installer in PS_INSTALL/disk1. Launch the installer using setup.bat. Click Next when you see the Welcome screen for PeopleTools 8.52.
  • Follow the steps as shown in the screen shots below.













  • This concludes the installation of PeopleTools 8.52.

Step 7: Installation PeopleSoft Application Software (HRMS 9.0):

  • Download and extract the step up files at PS_APP_HOME location on C:\.
  • Launch the installer with Setup.bat.
  • Follow the instructions as shown in the screenshots below.









  • This concludes the installation of PeopleSoft HRMS 9.0

Step8: Installing and configuring PeopleSoft Databases:

  • Go to the location C:\PT853\setup\PsMpDbInstall, double click setup.exe
  • In the welcome screen click Next to continue and follow the instructions as shown in the screenshot below.

















Next steps continued in Part 3.


Vishal Modi

Environment what we are building consists of:

    • Operating System: Windows Server 2008 SP2.
    • Database Server: SQL Server 2008 with SP2.
    • PeopleSoft Application: PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0
    • PeopleTools: PeopleSoft PeopleTools 8.52
    • Web Server: Oracle Web Logic Server 10.3.4

The machine name given for this environment is WIN2K8 and currently only 1 user, the default username is Administrator and it is the local admin.

The below steps are performed with reference to the installation document of PeopleTools 8.52 on Microsoft SQL Serer provided by Oracle which can be found : This documentation is indeed very good and describes everything in very much details. Only drawback is that it is like 700 pages document and very tedious to go through. Hence thought of writing same instruction set but in bit easy format and more screenshots. 

Although, if you really want to understand the installation process and how each software works hand in hand with other then I highly recommend performing the installation with the Oracle PeopleSoft documentation.

If you have any issues during the Installation process, the best place to ask questions would be Oracle PeopleSoft Forums as the folks on that forums are certified PeopleSoft experts.

Step1: Download and install SQL Server 2008 with SP2:

  • Minimum requirement is Service Pack 2. If you have SP2 installed then you should see the SQL Server Native Client version as 2007.100.4000.00 as shown below in the screenshot. As of date, the latest Service Pack out for SQL Server 2008 is SP3 so even if you install SP3 then it works.


I am more of Microsoft Technologies person and not Oracle Technologies so installing and configuring SQL Server was easy. But still there are few important configurations which you need to perform in SQL too which you can find in the Oracle Documentations.

Step2: Download all software required from Oracle

  • Go to Https:// and sign in with your Oracle Account. If you do not have one, you can easily create one and its free registration.


  • On the Media Pack Search Page select Product Pack as PeopleSoft Enterprise and Platform as Microsoft Windows x64.

PS Ent X64

  • On the next page select PeopleSoft Human Resources Management System and Campus Solutions 9.0 Media Pack and select Continue.


  • On the next page download the following Softwares.

o PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0: Feature Pack - March 2011

o PeopleSoft Enterprise Human Resources Management System and Campus Solutions 9.0 Supplemental Installation Information (Revision 3)

o PeopleSoft PeopleTools 8.52 Disc 1 of 3

o PeopleSoft PeopleTools 8.52 Disc 2 of 3

o PeopleSoft PeopleTools 8.52 Disc 3 of 3

o Tuxedo 10gR3 for MS Windows Server 2008 w/MS VS 2008 x86 32-bit

o JRockit JDK R28.1 for Java SE 6 with JRockit Mission Control 4.0.1 for Microsoft Windows (64-bit x86)

o Oracle WebLogic Server 11gR1 (10.3.4) Generic and Coherence

Step3: Installing JRockit for Microsoft Windows:

  • Unzip the downloaded file and double click the setup file. Click Next on the Welcome screen window.


  • Change the installation directory to C:\Program Files\Java\jrockit-jdk1.6.0_20-R28.1.0-4.0.1 and click next


  • Keep the default values on all other pages and as shown in below screen shots.






  • This concludes the installation of JRockit.

Step4: Installing Oracle WebLogic on Windows:

  • Save the installation file wls_generic.jar from Oracle EDelivery in the directory called WLS_Install on C:\
  • Open a command prompt and go to WLS_INSTALL.
  • Set the environment variable JAVA_HOME to be the location where you installed the JRockit and Use the following command to launch the installer.


set JAVA_HOME=”C:\Program Files\Java\jrockit-jdk1.6.0_20-R28.1.0”

%JAVA_HOME%\bin\java -jar wls1034_generic.jar -mode=GUI -log=C:\WLS_Install\Wls1034Install.log


  • Wait for few seconds or also this might take few minutes and the Oracle WebLogic Installer Window will come up. Follow the instructionas as shown in the screenshots for next installation steps.



Remove the check box which says “I wish to receive security updates via My Oracle Support” . And click yes to remain uninformed for next 2 windows.










  • This concludes the Installation of Oracle Web Logic Server

Step5: Installing Oracle Tuxedo:

  • Save the zip file to a temporary directory on your local system, referred to in this documentation as TUX_INSTALL.. Extract the files into TUX_INSTALL.
  • First you need to designate an existing user or create a new user such as TUXADM to be the Application Server Administrator. The Application Server Administrator and not the Windows Administrator. This user will install Oracle Tuxedo. The designated user must be a local Microsoft Windows administrator and must have full system privileges. The PeopleSoft PeopleTools 8.52 program for the Oracle Tuxedo installation creates a new service for Microsoft Windows called “ORACLE ProcMGR V10gR3 with VS2008” for which you need administrator privileges. Administrator rights are required since system registry settings are updated. Once this new service is created, you must reboot to start it.
  • To designate the Application Server Administrator:

1. To add the user, add the user ID by choosing Start, Settings, Control Panel, Administrative Tools, Computer Management, Local Users and Groups.

2. Expand Local Users and Groups.

3. If the user ID does not yet exist, highlight the Users folder, and select Action, New User.

4. On the New User dialog box, specify the information for the new account. Make sure to deselect the User must change password at next logon check box.

5. Expand the Groups folder.

6. Right-click the Administrators group, and select All Tasks, Add to Group, Add.

7. Click Locations to select the local machine or the network domain in which you created the new user.

8. Enter the new user name you created in the object names box.

9. Click OK, and click Apply and OK again to accept the changes.

  • Double-click TUX_INSTALL\tuxedo10gR3_32_win_2k8_x86_VS2008.exe to begin the installation process. Click OK on the initial window.
  • Follow the steps shown in screenshots below.














  • Go to Windows –> Services


  • Instead of Administrator use the User account name which you created in the first few steps of Oracle Tuxedo Installation.


  • This concludes the installation and configuration of Oracle Tuxedo.

Next steps continued in Part 2.


Vishal Modi

Tuesday, July 12, 2011 #

Today we are glad to announce HERMES, an Open Source Infrastructure for publish subscribe messaging model based on MongoDB and RESTful Services.


This is 8th release of an open source project from TellagoDevLabs on Codeplex. Hermes is months of hard work by us, including Silvio Massari, Jose Romaniello and Gustavo Machado.


Hermes is not BizTalk Server. BizTalk Server has pub-sub mechanism in its infrastructure but in very traditional way and it hasn’t provided a foundation that can be seamlessly used by any .NET application. BizTalk pushes the message to its subscribers. If the subscribers are down, BizTalk retries it with the retry configurations. Even after all the retries, it suspends the message. In Hermes model, it not only pushes the message to the subscriber but also the Subscriber can come and poll for the message. Though, Hermes is not a message broker. Hermes does not care about what message it has been sent to what subscriber. Also, all the transformation are taken care by the subscriber and this removes that responsibility of the messaging engine of Hermes. Solely, Pub/Sub.


Hermes is over HTTP so it can be used by any Platform which makes everything really easy. Mostly all the platforms today have capability to communicate over HTTP. Hermes is very light weight and it can run easily on premise.  Check, how to setup Hermes on your machine. Also we are looking forward to test Hermes on “The Cloud”.


Hermes uses MongoDB to store its messages. MongoDB, which itself is ridiculously fast and hence, Hermes is very very fast. Using MongoDB, it made it extremely easy to store, partition and index high volumes of messages for a large number of topics and subscriptions.  Hermes also has an Admin Portal where you can administer Topics, Groups, Publishers, Subscribers and some statistics. You can even push messages through this portal. We are currently working on enhancing this portal.


We also provide a Client Library for C#. Using this library, it becomes fairly simple to create Groups, Topics, Subscriptions etc.  You can find a sample on how to use this library with the source code.


Licensing: Hermes is using BSD license. Completely Open Source.


You can check the Hermes documentation here. Read more about Hermes annoucement on Jesus Rodriguez blog post.


What’s Next:

  • Enhance the Administration Portal of Hermes.
  • Provide more sample applications using Hermes.
  • Enhance the REST API.
  • Build a JavaScript Client Library.
  • Hermes deployment on the “Cloud”. (AmazonEC2 and Windows Azure)
  • Explore new Messaging patterns.


Give it a try with Hermes and we are looking forward to hear feedback from you.




Vishal Mody

Monday, July 11, 2011 #

Hi there,


Recently we had a requirement to integrate a RESTful Service with BizTalk Server. Well no biggie. You can use WCF – Custom Adapter and use webHTTP binding and add a webHttp Endpoint behavior. Wala. Easy to say, little bit tricky to do.


That all is fine, but what if you want to have a polling receive location which needs to go and do an HTTP GET to a RESTful Service. Aahh!! That’s even more trickier. Bunch of you reading this post would have already thought about some or other way of doing it.


1. Create a basic windows service which runs at scheduled time and drops a message into BizTalk and Biztalk picks up, a RESTful send port subscribes to that message and do the regular RESTful call.


2. Have a SQL Task to drop a message and have a RESTful SendPort to do the regular RESTful call.


3. Many more way..


But what if we can have a Receive Port itself polling at regular interval and make the RESTful Service call? This eliminates the need of unnecessary windows service or the SQL Task or any other triggering process you think of. Cool right..!!


So I came across the BizTalk Scheduled Task Adapter.


This is a task scheduling adapter which can execute a prescribed task at a configured time. It comes with few default scheduling tasks like XmlString, FileReader, HttpDownload. Also has few version of it out there which can work with almost all versions of BizTalk Server. Lot of people are using it without any issues.


How does it solve our scenario of invoking RESTful Service?


Well, I decided to write a custom Task for it which will be invoking the RESTful Service. I tried to make this component pretty generic so that anyone can use it but ofcourse, it also depends upon type of RESTful service you are invoking. Few might need authentication, keys etc. You can always extend it according to your needs. Anyways, below is how you can use it.


1. Download and install the BizTalk Scheduled Task Adapter. Here is a blog post on how you can use the defaults Tasks which comes with it.


2. Download and Open the RESTServiceAdapterProvider Project in Visual Studio. Compile the code and GAC the assembly if it does not do it by itself.


3. Open BizTalk Server Admin Console and create a new Receive Port, Receive Location under your application.


4. In the receive location properties, Adapter type = Scheduler. This is the name you give to the BizTalk Scheduled Task Adapter while configuring it. If you don’t see this make sure you go to the Platform Setting à Adapters à New Adapter and from the drop down select the Schedule Adapter and name it whatever you want. In my case, I named it as Scheduler.


5. Next click Configure next the Adapter Type. In the configuration window, type the name of Schedule Task you want to give. In this case “RESTfulScheduler”


6. Next click the Schedule tab on this window and specify the time you want this scheduler to run.


7. Next click the Task tab on the same window and under the Class, click Find Task and Click browse under Assembly Qualified Type Name and select the RESTServiceAdapterProvider.dll from the file location of the RESTServiceAdapterProvider project.

8. In the Assembly Qualified Type Name, select RESTProvider and click Select and its fully qualified name will appear at the bottom and click OK.

9. If you get Invalid Assembly class selected, make sure you Gac the RestProvider dll, close the BTS Admin Console, reopen it and restart the HostInstance and try again.

10. Next specify the URL, Content Type, WebMethod and click Apply, OK.

11. Once you are done configuring, you will see the URI as : schedule://TimeSpan/RESTfulScheduler

12. Next is according to your requirements for the message. You can have pipeline component doing bunch of stuff or have orchestration, schemas, maps, business rules for this message or have a send port subscribing to this message. Anything.


You can download the source code of the RESTfulAdapterProvider here


So, above you saw way of configuring a BizTalk Receive Location Polling a RESTful Service. Thanks for reading.



-Vishal Mody

Friday, July 1, 2011 #

Tellago Studios proudly announces its newest product, a third one within a year of time : TELESHARP

.NET Configuration Management has always been a nightmare for any enterprise. TeleSharp is an innovative product that addresses the most common challenges of .NET applications in the enterprise. After years of struggle developing and managing large .NET applications, we decided to create a tool that makes .NET applications truly agile.

You can read more about Telesharp and what difference it can make into your enterprise. Also if you want to see Telesharp in action, check the videos about it.

Click here to get more information about TeleSharp trial version!

Click here to register for the TeleSharp webinar on July 6th from 2PM - 3PM EST.






Tuesday, June 7, 2011 #

Recently I was building a VM for a BizTalk 2006 R2 project.  My VM configuration was :


  • Windows 2003 R2
  • SQL 2005 with SP4
  • Visual Studio 2005 with SP1
  • BizTalk Server 2006R2 


I installed the BizTalk Server 2006 R2 SP1 update from the Windows Update.  Life was good so far. 


Next I got requirement to use WCF SQL adapter and there I went and started installing the pre-requisite for it. 


1.   WCF LOB Adapter SDK SP2 


2.  Microsoft BizTalk Adapter for SQL Server.


After that I went and tried to Add the Adapter metadata but then I did not see the WCF – SQL option itself. I was wondering what happened. I did some research and came across this blog post which told to change the BizTalk Version Number manually in the registry. I did that and reinstalled/repaired the packages like multiple times but in vain.


Finally I came across Microsoft’s this post which describes few issues which the BizTalk Server 2006 R2 SP1 update creates. 

What’s the fix then??


Install the BizTalk Server 2006 R2 SP1 Cumulative Update.


Hope this helps.





Wednesday, May 4, 2011 #

Hi there,

After the successful launch of the new website for Tellago, today we announce the new series of webinar’s called the Tellago Technology Updates. Today in the fast growing IT Industry it is very difficult to stay up-to-date with the latest and greatest Technologies out there in the market. Doesn’t matter if you are a Developer or an Architect or CTO for a company but you are every now and then challenged to evaluate new technologies and implement them.

Understanding that challenge, we at Tellago had started a weekly Tellago Technology Dojo where we have open discussion about the latest technologies out there. This Technology Dojo was a great success and today we are happy to announce a similar version of the Dojo as the Tellago Technology Updates. These are a montly series of webinars intended to help decision makers, developers and IT Professionals to understand the latest technology trends in the software industry as well as the strategies to leverage them in their organizations. These webinars will cover emerging technologies in the software industry from a practical standpoint that reflects the perspective of decision makers, developers and IT professionals.

We try to stay away from boring formal presentations and instead foment a practical dialog with the attendees in which we help them to understand the benefits and challenges of adopting specific technologies in their organizations.


  • NoSQL databases for the .NET developer: What’s the fuss all about?     

Date:  May 24 2011 - 2:00pm - 3:00pm EST 

NOSQL (Not Only SQL) databases are one of the hottest technology trends in the software industry. Ranging from web companies like Facebook, Foursquare, Twitter to IT power houses such as the US Federal Government, Banks or NASA; the number of companies that invest in the NOSQL paradigm as part of their infrastructure is growing exponentially. What is this NOSQL movement? What are the different types of NOSQL databases? What are the real advantages, challenges and ROIs? Can we leverage NOSQL databases from my .NET applications? This webinar will present an overview of the NOSQL movement from the perspectives of a .NET developer. We will explore the different types of NOSQL databases as well as their .NET interfaces. Finally, we will present a series of real world examples that illustrate how other companies have taken advantage of NOSQL databases as part of their infrastructure. 

  • I like IPhone and Android but I am a .NET developer: Developing .NET applications for IPhone and Android  

Date: Jun 21 2011 - 2:00pm - 3:00pm EST

Do you have an investment in Microsoft technologies but are starting to develop mobile applications for the IPhone, IPad and Android devices?
Wouldn’t you love to be able to build IPhone, IPad and Android applications using the .NET framework? After years of working with Microsoft.NET-based solutions, your developers have become very proficient at delivering solutions using Microsoft technologies. Now your business and customers are looking to build applications that target the IPhone, IPad and Android ecosystems. Can you reuse your existing investment in .NET technologies? This session will highlight the strategies for developing IPhone, IPad and Android applications using the .NET Framework. The session will explore the existing technologies that make this possible as well as challenges and benefits compared to alternative approaches. Our practical viewpoint will help you to start strategizing how to extend your existing investment in .NET technologies to the IPhone, IPad and Android ecosystems. We will share real world stories of companies that already invested in this path and we will explore different ideas to get you started.

Thanks and looking forward to see you at the Tellago Technology Updates.


Vishal Mody


Tuesday, February 15, 2011 #

Hi there,

Microsoft is hosting the first edition of their annual TechReddy conference. TechReady is an internal Microsoft conference but Microsoft invited Tellago Studios to present a session about how to enable Agile SOA Governance on the Microsoft platform using our recently release product: SO-Aware.

As part of our session, we will take a look at the current challenges that organizations face when enabling SOA governance capabilities on the Microsoft platform and how organizations can benefit from  more agile, lightweight and modern SOA governance models.

The session will provide a practical view to the role of Tellago Studios' SO-Aware as an essential technology to enable native SOA governance on the Microsoft platform. We will explore in detail important capabilities of SO-Aware such as

  • Centralized service repository
  • Centralized configuration management
  • Service testing
  • Monitoring
  • Transparent integration with technologies such as Visual Studio, BizTalk Server, Windows Server & Azure AppFabric among many others

But the fun doesn't stop there.....

As part of this session, we will showcase for the first time our upcoming SO-Aware Test Workbench product which enables load and functional web service testing capabilities on the Microsoft technology stack.

SO-Aware Test Workbench provides developers with a visually rich environment to model and control the execution of load and functional tests in a SOA infrastructure. This tool includes the first native WCF load testing engine allowing developers to transparently load test applications built on Microsoft's service oriented technologies such as WCF, BizTalk Server or the Windows Server or Azure AppFabric.


Monday, February 7, 2011 #

A few months ago myself and colleagues had open sourced the BizTalk Data Services. We were meanwhile working on other artifacts which comes along with BizTalk Server like the “Business Rules Engine”.  We are happy to announce the first version of BRE Data Services. BRE Data Services is a same concept which we covered through BTS Data Services, providing a RESTFul OData – based API to interact with the Business Rules Engine via HTTP using ATOM Publishing Protocol or JSON as the encoding mechanism.
In the first version release, we mainly focused on the browsing, querying and searching BRE artifacts via a RESTFul interface. Also along with that we provide the functionality to execute Business Rules by inserting the Facts for policies via the IUpdatable implementation of WCF Data Services.
The BRE Data Services API provides a lightweight interface for managing Business Rules Engine artifacts such as Policies, Rules, Vocabularies, Conditions, Actions, Facts etc. The following are some examples which details some of the available features in the current version of the API.
Basic Querying:
Querying BRE Policies
Querying BRE Rules
Querying BRE Vocabularies
The BRE Data Services API also leverages WCF Data Services to enable navigation across related different BRE objects.
Querying a specific Policy
Querying a specific Rule
Querying all Rules under a Policy
Querying all Facts under a Policy
Querying all Actions for a specific Rule
Querying all Conditions for a specific Rule
Querying a specific Vocabulary:
With the BRE Data Services, we also provide the functionality of executing a particular policy via HTTP. There are couple of ways you can do that though the API.
Ø First is though Service Operations feature of WCF Data Services in which you can execute the Facts by passing them in the URL itself. This is a very simple implementations of the executing the policies due to the limitations & restrictions (only primitive types of input parameters which can be passed) currently of the Service Operations of the WCF Data Services. Below is a code sample. 

              Below is a traced Request/Response message.             
Ø Second is through the IUpdatable Interface of WCF Data Services. In this method, you can first query the rule which you want to execute and then inserts Facts for that particular Rules and finally when you perform the SaveChanges() call for the IUpdatable Interface API, it executes the policy with the facts which you inserted at runtime. Below is a sample of client side code. Due to the limitations of current version of WCF Data Services where there is no way you can return back the updates happening on the service side back to the client via the SaveChanges() method. Here we are executing the rule passing a serialized XML as Facts and there is no changes made to any data where we can query back to fetch the changes. This is overcome though the first way to executing the policies which is by executing it as a Service Operation call.
This actually generates a AtomPub message shown as below:
POST /Tellago.BRE.REST.ServiceHost/BREMananagementService.svc/$batch HTTP/1.1
User-Agent: Microsoft ADO.NET Data Services
DataServiceVersion: 1.0;NetFx
MaxDataServiceVersion: 2.0;NetFx
Accept: application/atom+xml,application/xml
Accept-Charset: UTF-8
Content-Type: multipart/mixed; boundary=batch_6b9a5ced-5ecb-4585-940a-9d5e704c28c7
Host: localhost:8080
Content-Length: 1481
Expect: 100-continue
Content-Type: multipart/mixed; boundary=changeset_184a8c59-a714-4ba9-bb3d-889a88fe24bf
Content-Type: application/http
Content-Transfer-Encoding: binary
MERGE http://localhost:8080/Tellago.BRE.REST.ServiceHost/BREMananagementService.svc/Facts('TestPolicy') HTTP/1.1
Content-ID: 4
Content-Type: application/atom+xml;type=entry
Content-Length: 927
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<entry xmlns:d="" xmlns:m="" xmlns="">
  <category scheme="" term="Tellago.BRE.REST.Resources.Fact" />
  <title />
    <name />
  <content type="application/xml">
      <d:FactInstance>&lt;ns0:LoanStatus xmlns:ns0=""&gt;&lt;Age&gt;10&lt;/Age&gt;&lt;Status&gt;true&lt;/Status&gt;&lt;/ns0:LoanStatus&gt;</d:FactInstance>
The installation of the BRE Data Services is pretty straight forward.
·         Create a new IIS website say BREDataServices.
·         Download the SourceCode from TellagoCodeplex and copy the content from Tellago.BRE.REST.ServiceHost to the physical location of the above created website.

·         The appPool account running the website should have admin access to the BizTalkRuleEngineDb database.

·         TheRight click the BREManagementService.svc in the IIS ContentView for the website and wala..

The BRE Data Services API is an experiment intended to bring the capabilities of RESTful/OData based services to the Traditional BTS/BRE Solutions. The future releases will target on technologies like BAM, ESB Toolkit.
This version has been tested with various version of BizTalk Server and we have uploaded the source code to our Tellago's DevLabs workspace at Codeplex. I hope you guys enjoy this release.
Keep an eye on our new releases @ Tellago Codeplex. We are working on various other Biztalk Artifacts like BAM, ESB Toolkit.
Till than happy BizzRuling…!!!
Vishal Mody


Friday, January 7, 2011 #

Hello folks,


If you are implementing a service oriented architecture, and are unsure of the best governance approach to follow, then this webinar is a must-attend event for you.  We will discuss why SO-Aware is the more efficient and interoperable alternative to traditional UDDI-based SOA-governance.


Specifically, we will address the differences between UDDI and SO-Aware in terms of service discovery, configuration, and policy resolution.  Finally, we will address why the REST/Odata based model implemented by SO-Aware enables the most efficient governance not only for WCF but for BizTalk, the Windows Server AppFabric and the Windows Azure AppFabric as well.


Join us on January 26th at 2:00 ET - to register, click here 






Wednesday, September 15, 2010 #

Shown below is one of the most easiest way to configure a BizTalk Receive Location which can receive any WCF Message based on the Binding type you provide in the configuration.  This uses the WCF Custom WebService Host Factory.
Where you can use this type of configurations?
·         Scenario where you need to send a WCF Message from .NET Code.
·         BizTalk Unit Testing.
·         Receive Locations which will be using ESB Toolkit receive locations.
·         and Many more.
Anyways, below are the steps:
- Create a IIS Virtual Directory and name it with some relevant name, say “Testing”. (Make sure the AppPool identity you select has proper priviledges.)
- Create a blank .svc file in the physical location of the directory, say “ReceiveMsg.svc”
- Open up that svc file in note pad and copy the below markup stuff in it.
<%@ ServiceHost Language="c#" Factory="Microsoft.BizTalk.Adapter.Wcf.Runtime.CustomWebServiceHostFactory, Microsoft.BizTalk.Adapter.Wcf.Runtime, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
- Next, open up BizTalk Admin Console and Create a Receive Port in whichever BizTalk App where you want the port to be.       
- Create a Receive Location for that Receive Port.
- Select the Transport Type as WCF-CustomIsolated.
- Next configure the WCF-CustomIsolated type. For the URI type "/Testing/ReceiveMsg.svc".
- For the binding you can select any WCF binding, here for the example I choose basicHTTPBinding. You can also configure the security configuration for this binding but lets leave it default for the example. Make sure you configure your client which sends the message according to same binding configurations.
- Pipeline: You can have your own Custom Pipeline or use BizTalk default ones. Here, lets keep it PassThruReceive.
- That’s it. Your receive location is configured and now just enable it.Next go to IIS and browse the ReceiveMsg.svc. You should see the below screenshot.
There are bunch of blog posts where it shows how you can send message to Biztalk though custom .net code. You can refer my previous blog post in which I have shown how you can use netNamedPipeBinding. One of my collegue Uri Katsir has blog post where he shows about WSHttpBinding.
Vishal Mody


Hi there everyone,

We have a Webinar coming up for BizTalk Governance using SO-Aware on Thursday, October 28th 2010 (2:00PM to 3:00PM EST). Like you guys might be knowing now that SO-Aware is a "WCF RESTful Registry solution" and its one of the attractive feature is Centralizing Configurations. This webinar will be showing you some of those features and also how you can use SO-Aware extensively with other BizTalk Solutions.

You can register/sign up here:

Meanwhile you can read this blog post from Jesus Rodriguez in which he talks more about Simpliying BizTalk Adapter Configurations using SO-Aware.


Thanks and Happy BizSoAwaring...!!!

 Vishal Mody

Sunday, August 15, 2010 #

Hey folks,

Recently, TellagoStudios released our first product SO-Aware and now there are couple of episodes discussing the architecture and different capabilities of SO-Aware available to view on Channel9. You can check out the videos and please send us some feedback about the product and also you can download the Express Edition of and product for free.  

Meet SO-Aware Part1 on Channel9.

Meet SO-Aware Part2 on Channel9.


Thanks and Happy SO-Awaring...!!! 

-Vishal Mody