Una vez que se haya configurado correctamente el nodo habilitado para Private Service Connect, trabajar con él se asemeja mucho al proceso de un nodo con extremos públicos, con solo dos ajustes esenciales en el flujo de trabajo estándar:
Durante la interacción con el nodo, usa la dirección IP estática de Private Service Connect junto con el puerto designado para la interacción que elijas, en lugar del extremo DNS estándar.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-03-27 (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."]]],[]]
