Árvore de páginas

Versões comparadas

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.
HTML

<div id="main-content" class="wiki-content group">
	<p>
	<div class="office-container">
		<a
			href="http://tdn.totvs.com/download/attachments/185741336/Integracao_usuarios.xlsx?version=2&modificationDate=1426682991000&api=v2"
			class="confluence-button office-editable" data-use-path-auth="false">Edit
			Document</a>
		<div class="office-document">
			<div id="panel1" style='display: block'>
				<table class="offconn-12"
					style='border: 1pt solid #c0c0c0; border-collapse: collapse; table-layout: fixed; width: 1524'
					border="0" cellspacing="0" cellpadding="0" bgcolor="#FFFFFF">
					<col width="89" />
					<col width="170" />
					<col width="365" />
					<col width="383" />
					<col width="517" />
					<tr style='height: 20.0px'>
						<td class="oc-0" rowspan="1" colspan="5">INTEGRATION FLUIG,
							ERP and IDENTITY</td>
					</tr>
					<tr style='height: 20.0px'>
						<td class="oc-1">MODULE</td>
						<td class="oc-1">INTEGRATION TYPE</td>
						<td class="oc-1">ERP (no IDM) &lt;=> Fluig (no IDM)</td>
						<td class="oc-1">ERP &lt;=> Fluig + IDM</td>
						<td class="oc-1">ERP + IDM &lt;=> Fluig + IDM</td>
					</tr>
					<tr style='height: 160.0px'>
						<td class="oc-2">EDM</td>
						<td class="oc-2">SOAP</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) CollegueId for business method</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) CollegueId for business method</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) ERP should carry out the following procedures
							to get the colleagueId on Fluig: - Query the user by e-mail on
							Fluig - Check whether the return is the internal registration of
							the ERP, and if not - Check whether the return is the IDP_ID of
							Identity - Send Fluig the ColleagueId according to information
							from the previous steps.</td>
					</tr>
					<tr style='height: 160.0px'>
						<td class="oc-2">WKF/BPM</td>
						<td class="oc-2">SOAP</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) CollegueId for business method</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) CollegueId for business method</td>
						<td class="oc-3">1) Integrator user and password for
							authentication 2) ERP should carry out the following procedures
							to get the colleagueId on Fluig: - Query the user by e-mail on
							Fluig - Check whether the return is the internal registration of
							the ERP, and if not - Check whether the return is the IDP_ID of
							Identity - Send Fluig the ColleagueId according to information
							from the previous steps.</td>
					</tr>
					<tr style='height: 20.0px'>
						<td class="oc-2">SOCIAL</td>
						<td class="oc-2">Public API (REST)</td>
						<td class="oc-4">1) Application user</td>
						<td class="oc-4">1) Application user</td>
						<td class="oc-4">1) Application user</td>
					</tr>
					<tr style='height: 40.0px'>
						<td class="oc-2">WCM</td>
						<td class="oc-2">Native schedule</td>
						<td class="oc-4">Fluig will standardize the technique to
							access external systems from a widget.</td>
						<td class="oc-4">Fluig will standardize the technique to
							access external systems from a widget.</td>
						<td class="oc-4">Fluig will standardize the technique to
							access external systems from a widget.</td>
					</tr>
					<tr style='height: 20.0px'>
						<td class="oc-5"></td>
						<td class="oc-5"></td>
						<td class="oc-1">REQUIREMENTS</td>
						<td class="oc-1">REQUIREMENTS</td>
						<td class="oc-1">REQUIREMENTS</td>
					</tr>
					<tr style='height: 140.0px'>
						<td class="oc-5"></td>
						<td class="oc-5"></td>
						<td class="oc-3">1) RM and Protheus - Execute the user
							synchronization wizard. The objective is to synchronize the
							registration field between ERP and Fluig 2) Logix - Configure the
							integration user 3) User's CollegueId must be the same on Fluig
							and ERP.</td>
						<td class="oc-3">1) RM and Protheus - Execute the user
							synchronization wizard. The objective is to synchronize the
							registration field between ERP and Fluig 2) Logix - Configure the
							integration user 3) User's CollegueId must be the same on Fluig
							and ERP.</td>
						<td class="oc-3">1) Create users on ERP and Fluig from
							provisioning via Identity.</td>
					</tr>
					<tr style='height: 20.0px'>
						<td class="oc-5"></td>
						<td class="oc-5"></td>
						<td class="oc-1">NOTES:</td>
						<td class="oc-1">NOTES:</td>
						<td class="oc-1">NOTES:</td>
					</tr>
					<tr style='height: 280.0px'>
						<td class="oc-5"></td>
						<td class="oc-5"></td>
						<td class="oc-3">1) The application user is created in the
							control panel of Fluig. Add an Oauth Provider type WCM. Add an
							Oauth App using the created provider. Select the Oauth App
							recently created and click the application user button. A token
							with permanent validity will be created for integration 2) We do
							not locate official documents from the user synchronization
							routine for Fluig on Datasul or Logix 3) We do not locate
							official documentation to consume WKF/BPM on the RM registered on
							the integration map.</td>
						<td class="oc-3">1) The application user is created in the
							control panel of Fluig. Add an Oauth Provider type WCM. Add an
							Oauth App using the created provider. Select the Oauth App
							recently created and click the application user button. A token
							with permanent validity will be created for integration 2) We do
							not locate official documentation to consume WKF/BPM on the RM
							registered on the integration map.</td>
						<td class="oc-3">1) The application user is created in the
							control panel of Fluig. Add an Oauth Provider type WCM. Add an
							Oauth App using the created provider. Select the Oauth App
							recently created and click the application user button. A token
							with permanent validity will be created for integration 2) The
							ECM 3.0 legacy databases will not have the registration field
							altered 3) We do not locate official documentation to consume
							WKF/BPM on the RM registered on the integration map.</td>
					</tr>
				</table>
				<style>
table.offconn-12 tr td.oc-0 {
	border-bottom: 1pt solid #000000;
	border-right: 1pt solid #c0c0c0;
	border-top: 1pt solid #c0c0c0;
	border-left: 1pt solid #000000;
	color: #FFFFFF;
	background: #92D050;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: justify;
	vertical-align: top
}
table.offconn-12 tr td.oc-1 {
	border-bottom: 1pt solid #000000;
	border-right: 1pt solid #000000;
	border-top: 1pt solid #000000;
	border-left: 1pt solid #000000;
	color: #000000;
	background: #FFFFFF;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: left;
	vertical-align: top
}
table.offconn-12 tr td.oc-2 {
	border-bottom: 1pt solid #000000;
	border-right: 1pt solid #000000;
	border-top: 1pt solid #000000;
	border-left: 1pt solid #000000;
	color: #000000;
	background: #FFFFFF;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: left;
	vertical-align: middle
}
table.offconn-12 tr td.oc-3 {
	border-bottom: 1pt solid #000000;
	border-right: 1pt solid #000000;
	border-top: 1pt solid #000000;
	border-left: 1pt solid #000000;
	color: #000000;
	background: #FFFFFF;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: justify;
	vertical-align: baseline
}
table.offconn-12 tr td.oc-4 {
	border-bottom: 1pt solid #000000;
	border-right: 1pt solid #000000;
	border-top: 1pt solid #000000;
	border-left: 1pt solid #000000;
	color: #000000;
	background: #FFFFFF;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: justify;
	vertical-align: top
}
table.offconn-12 tr td.oc-5 {
	border: 1pt solid #c0c0c0;
	color: #000000;
	background: #FFFFFF;
	font-family: Calibri;
	font-size: 11.0pt;
	font-style: normal;
	font-weight: normal;
	padding-left: 1px;
	padding-right: 1px;
	padding-top: 1px;
	text-align: justify;
	vertical-align: top
}
</style>
			</div>
		</div>
	</div>
	</p>
</div>