Depois que o nó ativado pelo Private Service Connect for configurado,
o trabalho com ele será semelhante ao processo de um nó com endpoints públicos,
com apenas dois ajustes essenciais no
fluxo de trabalho padrão:
Durante a interação com o nó, use o endereço IP estático do Private Service Connect
com a porta designada para a interação escolhida,
em vez do endpoint DNS padrão.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-03-06 UTC."],[[["This page explains how to set up a Private Service Connect endpoint for Blockchain Node Engine."],["To use this feature, you must first create a Private Service Connect-enabled node, noting that this configuration is permanent once the node is created."],["After creating the node, complete the setup by following the Private Service Connect configuration guide using the target service information from your node's output."],["Using a Private Service Connect-enabled node is similar to using a public node, but you must ensure the network is set up correctly and use the Private Service Connect static IP address instead of the standard DNS endpoint."],["If you have Private Service Connect enabled, be aware that a manual migration might be necessary to stay compatible with future updates, and you will receive notifications of any required actions."]]],[]]
