<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:24.0pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman",serif;
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:windowtext;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Times New Roman",serif;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Times New Roman",serif;
font-weight:bold;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Oregon GIS Community, anyone who is interested in publishing from ArcGIS Pro straight to ArcGIS Server may find this GeoNET posting by the Senior Product Engineer for ArcGIS
Enterprise, Philip Heede. This may help you decide whether you want or need to jump into the ArcGIS Portal side of Enterprise.<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td valign="top" style="padding:0in 0in 0in 0in">
<h1 style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:15.0pt;margin-left:0in">
<span style="font-size:18.0pt;font-family:"Helvetica",sans-serif;color:#333333;font-weight:normal"><a href="https://community.esri.com/?et=watches.email.idea_comment"><span style="color:#333333;text-decoration:none">GeoNet</span><span style="text-decoration:none">
</span></a><o:p></o:p></span></h1>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif;display:none"><o:p> </o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="100%" style="width:100.0%;background:white;-moz-border-radius: 8px;-webkit-border-radius: 8px;border-radius: 8px">
<tbody>
<tr style="height:285.0pt">
<td style="padding:7.5pt 0in 15.0pt 0in;height:285.0pt">
<h3 style="mso-margin-top-alt:7.5pt;margin-right:0in;margin-bottom:3.75pt;margin-left:0in">
<span style="font-size:13.0pt;font-family:"Helvetica",sans-serif;font-weight:normal">ArcGIS Pro Publish Services To ArcGIS Server
<o:p></o:p></span></h3>
<p class="MsoNormal"><span style="font-family:"Helvetica",sans-serif">new comment by
<a href="https://community.esri.com/people/pheede-esristaff">Philip Heede</a> <a href="https://community.esri.com/ideas/12258-arcgis-pro-publish-services-to-arcgis-server?commentID=68592#comment-68592">
View all comments on this idea</a> </span><span style="font-size:12.0pt;font-family:"Helvetica",sans-serif"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="mso-margin-top-alt:15.0pt;margin-right:0in;margin-bottom:15.0pt;margin-left:0in;text-align:center">
<span style="font-family:"Helvetica",sans-serif">
<hr size="1" width="100%" align="center">
</span></div>
<p><span style="font-family:"Helvetica",sans-serif">Hi Josh (and everyone else following this thread),<o:p></o:p></span></p>
<p style="min-height: 8pt"><span style="font-family:"Helvetica",sans-serif"> As we are finalizing ArcGIS Pro 2.3 and ArcGIS Enterprise 10.7, we are unfortunately falling a bit short of our original goals for the features related to publishing from Pro to a
standalone ArcGIS Server.<o:p></o:p></span></p>
<p style="min-height: 8pt"><span style="font-family:"Helvetica",sans-serif"> With ArcGIS Pro 2.3, it will be possible to publish map services (and related capabilities like feature services) to a standalone ArcGIS Server. Publishing will be via Python scripting
only, i.e. via arcpy-based scripts.<o:p></o:p></span></p>
<p style="min-height: 8pt"><span style="font-family:"Helvetica",sans-serif"> This is not everything that was originally planned and we will continue to add additional functionality in future releases of ArcGIS Pro.<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p style="border:none;padding:0in;min-height: 8pt"><span style="font-family:"Helvetica",sans-serif"> For ArcGIS Pro 2.4, due later in 2019, we plan to have a full publishing user experience within ArcGIS Pro in addition to the scripting-based experience being
introduced in ArcGIS Pro 2.3 here in January. After Pro 2.3, we also plan on adding support for publishing other service types beyond map services including image services, geoprocessing services, and more.<o:p></o:p></span></p>
</div>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">=============================<br>
David Mather, GISP<br>
Geospatial Data Administrator<br>
Geospatial Enterprise Office<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">Office of the State CIO</span><span style="font-size:10.0pt;color:#1F4E79"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F4E79">635 Capitol st NE # 150</span><span style="font-size:10.0pt;color:#1F4E79"><br>
Salem, OR 97301<br>
503-378-2166<br>
gis.oregon.gov<br>
=============================<br>
Data Classification: Level 1 - Published<br>
</span><span style="color:#1F4E79"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>