Quick Start (SOAP mode): Setting the execution context of a service using the Java API

The following Java code example sets the Run-As Invoker execution context to an example service named EncryptDocument .

    * This Java Quick Start uses the following JAR files 
    * 1. adobe-taskmanager-client.jar 
    * 2. adobe-livecycle-client.jar 
    * 3. adobe-usermanager-client.jar  
    * 4. activation.jar (required for SOAP mode) 
        * 5. axis.jar (required for SOAP mode) 
        * 6. commons-codec-1.3.jar (required for SOAP mode) 
        * 7. commons-collections-3.2.jar  (required for SOAP mode) 
        * 8. commons-discovery.jar (required for SOAP mode) 
        * 9. commons-logging.jar (required for SOAP mode) 
        * 10. dom3-xml-apis-2.5.0.jar (required for SOAP mode) 
        * 11. jaxen-1.1-beta-9.jar (required for SOAP mode) 
        * 12. jaxrpc.jar (required for SOAP mode) 
        * 13. log4j.jar (required for SOAP mode) 
        * 14. mail.jar (required for SOAP mode) 
        * 15. saaj.jar (required for SOAP mode) 
        * 16. wsdl4j.jar (required for SOAP mode) 
        * 17. xalan.jar (required for SOAP mode) 
        * 18. xbean.jar (required for SOAP mode) 
        * 19. xercesImpl.jar (required for SOAP mode) 
    *  The JBoss files must be kept in the jboss\bin\client folder. You can copy the client folder to  
    *  your local development environment and then include the 3 JBoss JAR files in your class path 
    *  These JAR files are located in the following path: 
    * <install directory>/sdk/client-libs/common 
    * If you want to invoke a remote forms server instance and there is a 
    * firewall between the client application and the server, then it is  
    * recommended that you use the SOAP mode. When using the SOAP mode,  
    * you have to include additional JAR files located in the following  
    * path 
    * <install directory>/sdk/client-libs/thirdparty 
    * For information about the SOAP  
    * mode and the additional JAR files that need to be included,  
    * see "Setting connection properties" in Programming  
    * with AEM Forms 
import java.util.*; 
import com.adobe.idp.dsc.clientsdk.ServiceClientFactory; 
import com.adobe.idp.dsc.clientsdk.ServiceClientFactoryProperties; 
import com.adobe.idp.dsc.registry.infomodel.ServiceConfiguration; 
import com.adobe.idp.dsc.registry.service.ModifyServiceConfigurationInfo; 
import com.adobe.idp.dsc.registry.service.client.ServiceRegistryClient; 
    * This Java quick start sets the Run-As Invoker to a service named EncryptDocument 
public class SetRunAsConfiguration { 
     public static void main(String[] args) { 
        //Set connection properties required to invoke AEM Forms 
        Properties connectionProps = new Properties(); 
        connectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_SOAP_ENDPOINT, "jnp://[server]:[port]"); 
        connectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE, "JBoss"); 
        connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_USERNAME, "tblue"); 
        connectionProps.setProperty(ServiceClientFactoryProperties.DSC_CREDENTIAL_PASSWORD, "password"); 
        //Create a ServiceRegistryClient object      
        ServiceClientFactory _factory = ServiceClientFactory.createInstance(connectionProps); 
        ServiceRegistryClient _src = new ServiceRegistryClient(_factory); 
        //Reference the EncryptDocument service 
        ServiceConfiguration _config  = _src.getHeadActiveConfiguration("EncryptDocument"); 
        //Set the RUN_AS_INVOKER execution context 
        ModifyServiceConfigurationInfo _configModifyInfo = new ModifyServiceConfigurationInfo(); 
        _config = _src.modifyConfiguration(_configModifyInfo); 
    }catch (Exception e) { 

// Ethnio survey code removed