Hi,
I am looking for any hints as to what files should I include in my
sipxconfig plugin which has no configuration options nor any GUI.
I need my optional ACD rpm to sneek in several additional sipx
processes so that they can be managed by the sipxsupervisor.
Anyway I see that I need to :
- create a process definition file and put it process.d directory
- create a shell script that starts,stops and configtests my process
- create sipxconfig plugin - a jar file with
a) a class that extends SipxService like this
public class VWACDEnterpriseServiceBusService extends SipxService {
public static final String BEAN_ID = "vwACDESBService";
}
b) sipxplugin.beans.xml with
<bean id="vwACDESBService"
class
="org.voiceworks.sipxconfig.service.VWACDEnterpriseServiceBusService"
parent="sipxService" scope="prototype">
<property name="processName" value="StompServer" />
<property name="bundles">
<set>
<ref bean="callCenterBundle" />
</set>
</property>
</bean>
Is this enough for "no gui" service ? (no changes do DB needed ?)
Can I include it in one of the existing bundles without any negative
consequences ?
How do I make this process active during my RPM installation ?
Pawel,
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
