Re-register an MGM

An MGM Membership Group Manager. May also be referred to as the Network Manager. It is a virtual node and Corda identity that acts as a central registrar for group membership. may need to update its own member-provided context; for example, as part of a platform upgrade or changes to its endpoint information. Additionally, an MGM that previously attempted to register but failed may wish to try again. The instructions on this page assume that you have completed the registration steps.

To re-register an MGM:

1. Send a re-registration request using the common registration/re-registration endpoint:

   • Bash
   • PowerShell

   export REGISTRATION_REQUEST='{"memberRegistrationRequest":{"context": '$REGISTRATION_CONTEXT'}}'
   curl --insecure -u admin:admin -d "$REGISTRATION_REQUEST" $API_URL/membership/$HOLDING_ID
   

   $REGISTER_RESPONSE = Invoke-RestMethod -SkipCertificateCheck  -Headers @{Authorization=("Basic {0}" -f $AUTH_INFO)} -Method Post -Uri "$API_URL/membership/$HOLDING_ID" -Body (ConvertTo-Json -Depth 4 @{
       memberRegistrationRequest = @{
           context = $REGISTRATION_CONTEXT
       }
   })
   $REGISTER_RESPONSE.registrationStatus
   

   This request should return a successful response with the status SUBMITTED. The cluster that hosts the MGM processes the request. You can check if the request was approved by checking the status of the registration request.

2. Upgrade the member CPIs Corda Package Installer. A signed ZIP/JAR combination of a CPB and a Group Policy File that defines not only the application code that a virtual node will run, but also the details of the MGM with which to register, and the details of network PKI requirements. to distribute the MGM’s MemberInfo to the members of the network.