Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. BlackBerry AtHoc Integrations
  4. IIM Push Button PostCap to SDK Migration Guide
  5. Migrate from PostCap to SDK

Migrate from PostCap to SDK

  1. Log in to IIM.
  2. Stop the capnode service.
  3. Obtain and download the capnode.zip folder that has the push button solution. Contact your BlackBerry AtHoc implementation engineer to download the ZIP file.
  4. Right-click the capnode.zip file and select extract to 
    C://Program files/capnode folder
    .
  5. Copy the following parameters to the 
    system.private.config
     file and modify the values as required:
    You can also add these values to the 
    system.config
     file. However, if you are using 
    system.config
     file, ensure that similar parameters are not included in 
    system_private.config 
    file. The parameter values in the 
    system_private.config
     file override the values in the
     system.config 
    file.
    # Value of this parameter can be SDK or PostCap.
# Since we are migrating to SDK keep the value as SDK
                          
    AlertPostingMechanism=SDK
SDKPostingTarget=True
                            
#
                                            
# Here replace <server.url.com> with actual server url.
# For example,(integration7.athoc.com)
 
    SDKAlertPosting.Url= https\://<server.url.com>/sdk/listener/listen.asp
    
#
                                                                        
# Provide the Org Id from the BlackBerry AtHoc site.
 
    SDKAlertPosting.VPS_ID=
                                        
# 
                                                
# Provide the BlackBerry AtHoc username.
# This user must have SDK posting privileges.
 
    SDKAlertPosting.Username=
    
#
                                                                                    
# This parameter indicates if the password provided in 
# SDKAlertPosting.Password Parameter is an encrypted 
# or plain text password.
# Initially the value of this parameter should be kept as ‘no’. 
# After the first run SDKAlertPosting.Password Parameter will be 
# updated by the IIM application with the encrypted password and the 
# value of SDKAlertPosting.IsPasswordEncrypted will be updated to ‘yes’ 
#                                    
 
    SDKAlertPosting.IsPasswordEncrypted=no
    
#
                                                
# Initially, you need to enter plain text password here. 
# After the first run it will get encrypted as explained above. 
 
    SDKAlertPosting.Password=
    
#    
                                            
#Parameters to custom map between Digital Input and AlertTemplate File.
#For detailed information about how to get common name for alert
#temapltes, see "Create alert template" section.
#
 
    DigitalInputToCommonName.1=<common name of IWS alert template1>
DigitalInputToCommonName.2=<common name of IWS alert template2> 
DigitalInputToCommonName.3=<common name of IWS alert template3>
DigitalInputToCommonName.4=<common name of IWS alert template4>
DigitalInputToCommonName.5=<common name of IWS alert template5>
DigitalInputToCommonName.6=<common name of IWS alert template6> 
DigitalInputToCommonName.7=<common name of IWS alert template7> 
DigitalInputToCommonName.8=<common name of IWS alert template8>
    
#
                                    
# Provide the relay number to be activated on successful Posting of 
# SDK alert to BlackBerry AtHoc 
 
    PushButtonActivator.Relay.PostedToIWS=1
    
#
                                    
# The following parameters are for the debounce mechanism. 
# The debounce mechanism ensures that IIM sees a network failure 
# on predefined (NumInputHighToTrigger) “consecutive” polling failures. 
# This is to prevent a quick voltage spike that can trigger the input.
#InputPollInterval is the duration between two consecutive relay polls. 
#
    InputPollInterval=200 
NumInputHighToTrigger=3
    
#
                                                
# The following parameters are for software improvements performed 
# in Connectivity Indicator only.
# When the number of CONSECUTIVE failures is equal to or greater than
# the value of ConnectivityProblemIndicatorCount the relay opens.
#
 
    ConnectivityProblemIndicatorCount=3 
delayBetweenRxPolls=7
ClosedRelayForMonitoring=5
  6. Remove the following post cap parameters from the 
    system.config
     and 
    system_private.config
     files:
    • CapPostingTarget=True
    • CapPostingTarget.capUrl=http\://alert.emn.com/syndication/PostCap
    • CapPostingTarget.user=
    • CapPostingTarget.password=
  7. Start the CapNode service.