Configure multiple Admin Servers in different domains simultaneously

-
Create an Admin Server as usual(Admin Server - > localhost:7001) in base_domain with default port.For Configuring the second Admin Server follow the instructions below.

Weblogic Changes -> Go to the Domain Configuration Wizard.

1. From Start Menu,select Programs->BEA Products >
   Tools >ConfigurationWizard

2. Select "Create a new Weblogic domain".

3. Select "Generate a domain configured automatically...." and
   click “Next”.

4. Select the username,password and the appropriate JDK(eg:
   C:\jdk1.5.0_18).

5. After that you will get a screen to customize,answer yes to that
   and change the port  to 7003 and leave the rest to default.

6. Give the name for the domain as “test_domain” and click “create”.

7. Create the new domain.

8. Start the Admin Server(testServer),Configure the required
   datasources and deploy EAR.

9. Modify your weblogic startup   script
   (C:\bea\user_projects\domains\test_domain\bin\startWebLogic.cmd).
   set the  server name in the  JAVA_OPTIONS variable.

10. set JAVA_OPTIONS=-Datg.dynamo.server.name=testServer %
    JAVA_OPTIONS%,before the line set SAVE_JAVA_OPTIONS=% 
    JAVA_OPTIONS%.

ATG Changes

ATG by  default set the RMI Port and Drp Port  as 8860 and 8850 for the Admin Server irrespectieve of domain.so you need to create new  ports  for the newly created testServer.

1.From Start Menu, select Run > type cmd > Go to C:\ATG\ATG9.1
  \home\bin
2.run the command   makeDynamoServer testServer 8861 8851.

Note: 
    
You will get rmiInitialisation Exception(JVM_BIND port already in use),if you fail to configure the DynamoServer.

After this you can deploy EAR's and start Running your application in both Admin Servers.

There is also another easy way to configure the  same with minimal changes -> Alternate Approach

Comments

Post a Comment

Popular posts from this blog

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more