[PDK] Creating a Dynamic Model for your Plug-in

Usually when you are creating a plug-in it is possible that you want to make changes on your model. For example, if you are working on a Input Adapter like the one we are creating here for RabbitMQ it is common that you want to support send data as String or as a ByteArray, and you want if you are going to send a String the input text to set the data should be coded as a String and if you want to send binary date (ByteArray) you want that the input text will be set like a binary field. This behavior it is common of the default activities at BusinessWorks. One example of that behavior it is on the Parse XML activity:

TIBCOBusinessStudio_2016-02-07_14-31-08TIBCOBusinessStudio_2016-02-07_14-32-54

TIBCOBusinessStudio_2016-02-07_14-31-24TIBCOBusinessStudio_2016-02-07_14-31-49

Ok, We understand now the behavior, but how can we do something like this? Ok, let’s go!

Continue reading

[PDK Series] Creating new categories for our configurations

In the previous post we talked about how to create our activities through the wizard the TIBCO BusinessWorks Studio for Designers gives us when we have installed the plug-in Development Kit, but when we want to add our configuration items at the activity we have two defaults options: “General” and “Advanced”.

But if you look at the built-in activities some of them have custom categories when it specifices some of the configuration. So, how we can do the same with our activities? Ok. Let’s do it!

The only thing we have to do, if in the moment we are creating the activity configuration items, do not check none of the defined value (General and Avanced) but to type the one you want. For example, as you can see here:

TIBCOBusinessStudio_2016-01-31_18-22-46

And that’s everything when you build the plug-in and use if inside your processes you are going to see something like this:

javaw_2016-01-31_18-27-22

[PDK Series] Coding a Real Plug-in Part II

After the use case description I’ve done on the previous post it’s time to start working on our plug-in, and the first thing to do that is talking about the enviornment that we need. So, we are going to use the Plug-in Development Kit 6.1 with the latest version of TIBCO AMX BusinessWorks we have available at the time I’m writing these that it is the TIBCO AMX BusinessWorks 6.3.

And the first thing we have to do it is to create the “plugin skeleton” or the plug-in structure (I don’t know if I should write plugin or plug-in, so I think I’m going to be changing from one form to another, I hope you can forgive me for that Open-mouthed smile ). To do that as it was explain on my first post about PDK, we have to launch the wizard the TIBCO AMX BusinessWorks Studio for Designers.

Continue reading

[PDK Series] Coding a Real Plug-in Part I

A few months ago, I’ve done some post series about the Plugin Development Kit from the new series release of TIBCO ActiveMatrix BusinessWorks. These posts covered the end-to-end cycle about plug-in development but they haven’t a fully logical sense, so the plug-in doesn’t do anything useful. These kind of posts are useful when you are trying to know how to start to a new feature or a tool but when you are truly working with it, doesn’t cover all the things you need.

And that’s the main reason I want to start this new series about PDK but with a true goal: We are going to do a fully plug-in for TIBCO BusinessWorks and we are going to talk about the things we have done, the problems we are facing and how to get through that. I hope that, with this approach, we have learn more deeply about how to work with this amazing feature the new TIBCO AMX BusinessWorks version gives us.

Continue reading

[PDK Series] Packaging our Custom Palette Using the Plugin Development Kit for BW 6.x

In the previous post, we saw how to create and deploy our Custom Palette inside a child TIBCO Business Studio (not the real one). In this chapter we are going to learn how to package the palette to distribute across different Business Studio’s and to use in a real environment. To do this, we start from the step we were in the previous post. And the next step is to export the model and runtime features.

Continue reading

[PDK Series] Using the Plugin Development Kit for BW 6.x

In the previous post, we learnt how to install the new Plugin Development Kit for BW 6.x to enable the capabilities to create our own custom palettes. Now, we are going to create our first one and test it in one real TIBCO BW process.

Continue reading

[PDK Series] Introducing the Plugin Development Kit for BW 6.x

When we are working usually with TIBCO BW we normally have the need to create additional elements that implements a common logic and we use for these cases several subprocesses that we share across our main BW processes. We even could increase the TIBCO BW capabilities via introducing Java Code our Java Custom Functions inside your processes and projects.  Ok, that’s right but sometimes we also have the need to create a complete set of actions to enable a new protocol or to implements a new logging API and so on. If we have a set of subprocesses we could create a ProjLib to do this event with custom icons for the processes but when we talk about Java Code we cannot have this posibility to create a unified set.

To do that, and to be able to pack this behavior into a new custom palette with its own brand, set of icons and documentations and to distribute to other people free or why not?  even in a paid model.

Ok, so if we want to do that in the new TIBCO BW 6.x series we have to learn how to use the Plug-in Development Kit for BW 6.x and that’s we are going to learn in these few post: from installation to deployment.

Continue reading