cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
580
Views
0
Helpful
3
Replies

how to set each jtapi.ini to each peer?

simon_new11
Level 1
Level 1

Hi all,

When search the JTAPI api, there is CiscoJtapiProperties#getUniqueJTAPIPropertiesPerPeer().

boolean getUniqueJTAPIPropertiesPerPeer()
This method returns true if the JTAPI is configured to use a unique JTAPIProperties object for each JtapiPeer, or false if JTAP is configured to share a single JTAPIProperties object for all peers.

Returns:
boolean
Since:
9.0

but is there modifier method for it, such as setUniqueJTAPIPropertiesPerPeer(boolean)?

or is there API to configure a unique JTAPIProperties object for each Provider object?

Thanks in advance.

Simon




3 Replies 3

smupadhy
Cisco Employee
Cisco Employee

Hi,

This configuration is loaded at startup, and cannot be changed once a Peer is created. And so, there appears to be no setter methods for this.

If I find some more information regarding this, I will post it here.

Thanks,

Hi Smita,

According the API, the setting cannot be changed after get provider from peer.

When we get peer from factory, I guess that we can change the content of  properties as bellow code:

  JtapiPeer peer = JtapiPeerFactory.getJtapiPeer(null);

  ((CiscoJtapiPeer)peer).getJtapiProperties();

  properties.setXXX(YYY);

   ....

   Provider provider1 = peer.getProvider(connectionStr1);


But for multiple clusters environment, can we use different properties for different providers? is code as bellow the right way?

  JtapiPeer peer = JtapiPeerFactory.getJtapiPeer(null);

  ((CiscoJtapiPeer)peer).getJtapiProperties();

properties.setXXX(YYY);

  ...

Provider provider1 = peer.getProvider(connectionStr1);

properties.setXXX(ZZZ);

  ...

  Provider provider2 = peer.getProvider(connectionStr2);


Thanks,

Simon

i don't think that will work. All providers would get the last properties set.

In multiple cluster scenario what properties would you like set different?

I have seen applications using 1 JVM per provider which talk to a central component that provides a multiple cluster view.