<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/discussions/f/best-practices/10905/what-would-be-the-best-practice-to-promote-appian-webservice-to-higher-environment</link><description>We have a process model which is exposed as a webservice. This is consumed by a SAIL rule. Now, what should be the Best Practice to package the service and promote to a higher environment?</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47950?ContentTypeID=1</link><pubDate>Fri, 25 Aug 2017 22:33:19 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6f3bcab2-5fb7-48f6-8bef-541cda4d76a9</guid><dc:creator>miteshp</dc:creator><description>Can you expose a process model as SOAP service using WebAPI? I guess those are for REST APIs.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47911?ContentTypeID=1</link><pubDate>Thu, 24 Aug 2017 14:14:39 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7256ce90-a853-424c-8dc5-1dc410bf04f5</guid><dc:creator>Shyam Bommakanti</dc:creator><description>Process models published as web service is not exportable Appian object, atleast not yet. So as other practitioners suggested manually create/document the steps for promoting.&lt;br /&gt;
&lt;br /&gt;
I suggest you look in to WebAPI.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47826?ContentTypeID=1</link><pubDate>Tue, 22 Aug 2017 17:37:32 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:6f7f656d-2b19-4c05-a20d-c18ee984d91c</guid><dc:creator>miteshp</dc:creator><description>I don&amp;#39;t think there is any good way. We are also publishing the process model as a service, explicitly, after migration to Production. We need to be careful to keep the service name same so that the constants (storing the service context part of the service WSDL URL)can have same value in all environment. We can keep a separate environment specific constant to just contain the server domain name part of the WSDL URL.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47799?ContentTypeID=1</link><pubDate>Mon, 21 Aug 2017 20:09:29 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:156ce484-8687-4f00-a025-631793e74fae</guid><dc:creator>senthilarumugamr</dc:creator><description>Mohamed, that would be right thing to do when Appian is consuming an external service. The case here is when Appian Process Model is exposed as webservice and Application package doesn&amp;#39;t have any means to package such webservices. So far, looks like the webservices need to be created manually in higher environment.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47743?ContentTypeID=1</link><pubDate>Sun, 20 Aug 2017 15:17:06 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ce8ca38a-d17a-4062-aea9-8f90c165f25b</guid><dc:creator>mohamedt808</dc:creator><description>One thing i would like to suggest if the same Service is used in the SAIL rule.You can write an Expression rule to derive the endpoints in each environment.  Parametrise the environemnt url part  using constants, and use them in the rule  as they would differ for each environement, after deploying you can update the constant to hold the current Environrment value.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47734?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 17:22:38 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:816dd4e3-cc20-4551-8fd9-18d7834f860c</guid><dc:creator>senthilarumugamr</dc:creator><description>Thank you! Documentation does not contain that info though.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be the Best Practice to promote Appian webservice to higher environment?</title><link>https://community.appian.com/thread/47720?ContentTypeID=1</link><pubDate>Fri, 18 Aug 2017 07:17:07 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:eab9d136-d533-4f49-b50a-5e537c2e750a</guid><dc:creator>sravanis</dc:creator><description>Hi,&lt;br /&gt;
&lt;br /&gt;
Please go through the below link.  &lt;br /&gt;
&lt;a href="https://docs.appian.com/suite/help/17.2/Scaling_Application_Development.html"&gt;docs.appian.com/.../Scaling_Application_Development.html&lt;/a&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>