Service Registry requires the following in order to work correctly:
The Registry must be able to access external web sites
The Application Server domain for the Registry must have enough memory available to it
Any registry object can have an ExternalLink object, which specifies an external URL associated with that registry object. Any Service object can have a ServiceBinding, which can also point to an external URL. In order for users to create ExternalLink and ServiceBinding objects, Service Registry must be able to validate the URL, and this task requires access to external web sites. If the Registry is deployed behind a firewall, you need to set a proxy configuration that allows this access.
Proxy configuration requires you to specify a web proxy host and port as Java Virtual Machine (JVM) options of the Application Server domain where Service Registry is deployed.
It is also possible for the Registry to run out of memory. To prevent this problem from occurring, configure a JVM option to increase the memory available to the Application Server domain for the Registry.
Perform the following task to configure JVM options for the Registry.
Log in to the Application Server Admin Console as described in To Use the Application Server Admin Console.
Expand the Configurations node.
Expand the server node, server-config (Admin Config).
Click JVM Settings.
Click the JVM Options tab.
Click Add JVM Option.
In the text field, type the following (all on one line):
-Dhttp.proxyHost=hostname.domainname -Dhttp.proxyPort=8080 -Dhttp.nonProxyHosts=localhost |
The port value is usually 8080. If the port is different in your location, specify the correct value.
Click Add JVM Option again.
In the text field, type the following (all on one line):
-XX:MaxPermSize=128m |
Click Save.
Follow the instructions in To Stop and Restart the Application Server Domain for the Registry.