When you have configured 2 Weblogic servers as one cluster, you need to ensure the 2 servers can communicate with one another to tell one server it's actions. To do this, you use multicasting.
Weblogic Coherence comes with it's own multi-testing script that you can use to test the connection between the servers. This multcasting script (simply called multcast-test.sh) can be located within the $MW_HOME/coherence_3_7/bin directory.
One of the better Oracle documents out here provides you an example on how to test multicasting between servers
The simple execution of the multicasting is be running the following command
multitest-test.sh
This will essentially run the script and determine if the server you're running on has multicasting enabled. You will get something similar (which basically showed that it's sending the packet to itself. Repeat this process on both servers to ensure it can send and receive the packets
Tue Mar 17 16:11:03 EST 2008: Sent packet 1.
Tue Mar 17 16:11:03 EST 2008: Received test packet 1 from self.
Tue Mar 17 16:11:05 EST 2008: Sent packet 2.
Tue Mar 17 16:11:05 EST 2008: Received test packet 2 from self.
Tue Mar 17 16:11:07 EST 2008: Sent packet 3.
Tue Mar 17 16:11:07 EST 2008: Received test packet 3 from self.
Testing multicasting between 2 servers
The next process is to try and send the package to another server via multicasting.
To do this, you need to pass the multicast IP address and run the script on both servers. You can retrieve the multicast IP address by running the netstat -g command. The IP address should be between 224.0.0.0 to 239.255.255.255 (as these are the IP ranges for multicasting). (lets pretend it's 231.10.10.11) Once you have that, incorporate it when running the script as a argument along with the UDP protocol number (try 9000).
./multicast-test.sh -group 231.10.10.11:9000
Once executed, on one server, do the same on the other server and determine if the packets are now being received by the other server, has presented within the test multicasting example.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...