Guest
Welcome login


TIBCOmmunity > Products > ActiveMatrix SOA > Service Grid > Conversations
Home   Members Communities
Conversations () Resources () Blogs ()

Service Grid

Up to Conversations in Service Grid

This Question is Answered

1 "helpful" answer available (2 pts)

Click to view Sai Boyedapu's profile Dabbler

non service related BW components - build/deployment to AMX
Created on: Feb 8, 2010 5:21 PM
Created by: Sai Boyedapu

Hi,
Is is possible to have a non-service related businessworks component as a part of a composite? i.e it appears as a hanging component without any mapping from the services?

 

As a sample, I did the following:

1) created a AMX project

2) created a composite with only a bw component that maps to bw project with no services, the bw project does contain a process with a timer starter activity

3) created the .saf/.zip for the composite and deployed the same to AMX admin The timer based bw process fails to start in the above case.

 

For the same bw if I create an ear first, convert it to an .zip (service assembly) using ear2sa utility, the bw process starts as expected.

 

Thanks,

Tags: activematrix, bw_service_engine, activematrix_service_grid
Click to view seshasai Kotipalli's profile Enthusiast
seshasai Kotipalli
271 posts since
Aug 13, 2008
1. Feb 8, 2010 6:45 PM in response to: Sai Boyedapu
Re: non service related BW components - build/deployment to AMX

Did you check if the ear file that BWComponent is pointing to has the timer based process added?

 

Check the example located at http://www.tibcommunity.com/message/35981#35981

Click to view Sai Boyedapu's profile Dabbler
Sai Boyedapu
35 posts since
Oct 9, 2008
2. Feb 9, 2010 2:28 PM in response to: seshasai Kotipalli
Re: non service related BW components - build/deployment to AMX

Thanks for the inputs! This worked once I added non-service type bw processes into the process archive settings in the archive. The .archive was created automatically upon configuring the BWSE component in the composite to an existing BW project. Unlike traditional bw designer the starter activities didnot get automatically added to the .par

 

It is intersting to note that when I was testing composites for a service related component - I didnot have to add the webservice agent nor any bw process to the process archive for the service assembly to work. Should the process not be the consistent for all types of processes?

Click to view seshasai Kotipalli's profile Enthusiast
seshasai Kotipalli
271 posts since
Aug 13, 2008
3. Feb 9, 2010 3:56 PM in response to: Sai Boyedapu
Re: non service related BW components - build/deployment to AMX

Service activity and invoke partner are little different. They are added to the ear if you expose them in the BWSE component in composite. But in case of other processes, you might have lot of processes in your designer project and you may not want to add all of them to the archive. Also, once you import existing BW project, you can add services and references. Once you do this, they get automatically added. But if you create a non-service based process, you will have to do the above steps.

 

Even in traditional designer, you need to add the process starters manually, but not the dependencies like schemas, subprocesses etc. The same is true in case of BWSE/DABS also.

Click to view Sai Boyedapu's profile Dabbler
Sai Boyedapu
35 posts since
Oct 9, 2008
4. Feb 9, 2010 5:01 PM in response to: seshasai Kotipalli
Re: non service related BW components - build/deployment to AMX

Thanks for the response. This answers my question.



More Like This

  • Retrieving data ...