RTC follow-up action plugin development

By -
Follow-up actions are events that are generated when the operation is completed.
A Participant is basically operational behavior that happens after a certain operation completed.

Extension point = com.ibm.team.process.service.operationParticipants
Implement the interface com.ibm.team.process.common.advice.runtime.IOperationParticipant
You have to create two plugin project 
1. Component  
2. Service

 Link for Component

Service Development 

Create Plug-in 

Open IDE(Eclipse)
Create a new Plug-in Development->Plug-in Project
Fill out the second dialog as follows, and select Next.


































Fill out the second dialog as follows, and select Finish.

Open MANIFEST.MF or Plugin.xml file for your project

From the Overview tab select This plug-in is a singleton. Save this file.

From the Dependencies tab, select the Add… button. Add the following four plug-ins to the list. After adding, save the file

com.ibm.team.process.common 
com.ibm.team.process.service 
com.ibm.team.workitem.common 
com.ibm.team.repository.common

 these are the few dependencies, for others functionality you may have to add others dependencies.
Like for 
SCM you have to add
* scm.common and * scm.service
repository.common and repository.service
Search for available .service and .common and add it

Adding Extensions 

Open MANIFEST.MF or Plugin.xml file for your project
GO to Extensions Tab

Search for operationParticipants 
Select com.ibm.team.process.service.operationParticipants

Under the Extension Element Details section. The operationId entry indicates which RTC operation we intend this plug-in to augment. When finished, save the file. 

 List of operation Id
Or you can get operation id from process template

Field
Value
id
com.test.rtc.ext.id
name
Any Name
operationId
com.ibm.team.workitem.operation.workItemSave


Download Template
More Info From IBM
Other Example

Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more