Transaction span two WLS managed servers (non-clustering)

(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?
- Does weblogic use XA to handle transaction between managed servers?
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?
Thanks in advance!
B.L.

Hi,
"benson" <[email protected]> wrote in message
news:[email protected]..
(Weblogic 6.1 - non-clustering version)
I have two managed servers configured on a single machine on different
ports, and I am not using clustering weblogic. Assuming I have EJB A
deployed on managed server 1, and EJB B deployed on managed server 2.
I want to have EJB A to invoke EJB B. In EJB A, I guess I will
probably create the InitialContext with the URL of managed server 2,
then do the JNDI look up and call EJB B.
My questions are:
- Can weblogic handle transaction that spans two managed servers
(non-clustering setting)?Yes, it can.
- Does weblogic use XA to handle transaction between managed servers?Yes, it does. Make sure you use TX DataSources. If the servers are connected
to different databases, TX DataSources should be based on connection pools
used XA drivers.
- Do I need to do any JTA code in order to achieve that (instead of
just letting the EJB container to handle the transaction for me)?No, you don't. WebLogic will take care about handling
distributed TXs.
Regards,
Slava Imeshev

Similar Messages

Two Managed Servers non-clustered problem

I have two managed servers each exactly the same just listening on different
          port in the same domain. When I start the second server I get a "Child
          exited " message reported in the first server's logs. This does not seem to
          affect the running of the server. Does anyone know why this happens. Note
          that both servers define the same jndi name for a stateless session bean.
          Could this be a problem>


Solaris 8. There is no information in any log relating to the message "Child
          Exited". Note that sometimes the message appears twice.
          "Kumar Allamraju" <[email protected]> wrote in message
          news:[email protected]..
          > what OS is this on?
          > This message may not be coming from WLS?
          > Can you post the error message or stacktrace?
          >
          > --
          > Kumar
          >
          > Paul
          >
          > > I have two managed servers each exactly the same just listening on
          different
          > > port in the same domain. When I start the second server I get a "Child
          > > exited " message reported in the first server's logs. This does not seem
          to
          > > affect the running of the server. Does anyone know why this happens.
          Note
          > > that both servers define the same jndi name for a stateless session
          bean.
          > > Could this be a problem>
          > >
          > >
          >

Use one agent for two different managment servers

Hi ,
Can one agent be connected to two different managment server in different domains ,
or do i have to install two agents in the same server to connect to each managment server .
thanks

Can one agent be connected to two different managment server in different domains
No
do i have to install two agents in the same server to connect to each managment server Yes.

Multiple managed servers, Multiple machines and Multiple clusters

Hi,
I have couple of applications to be deployed in high availabliity. I
have been a Tomcat/Apache guy so far. Yesterday night I read the whole admin doc
and tried some installations on the boxes. But have some confusion here.
Since our application is getting commercialised and I like to have 12 managed
serves on each of the three big linux servers and one windows machine as admin
server port 9002. 18 for each application in clustered environment. cluster of
18 for each application.
FIRST CONFUSION is
I want to use only one domain name. So I install weblogic81
on win box and call it dls and then I find out that I need to install weblogic81
as good as the one on win box on linux servers, not surpised, but during the installation
when it asked me for a domain name I was confused. No option to join the existing
domain that I created on my winbox.
Why??? So I type dls again.
Is there a way not to do all this as it may be creatign another domain and just
start nodemanager and not install domain at all ?
SECOND CONFUSION is
When I was installing weblogic on win machine as admin server. I was given
options of adding managed servers and clusters amd machines. So do we need to
have all the managed servers already running before I add them here or I can do
it later.
Thanks n Advance.
Vivke

http://www.rittmanmead.com/2010/07/obiee-11gr1-scaleout-clustering-and-high-availability/
hope it helps

Howto Programatically discover clusters, admin server, managed servers

Hi,
          I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
          I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
          I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
          Is this possible.
          Cheers,
          Keith

Keith Hyland <> writes:
          > I'm want to programatically discover what clusters, admins servers, and managed servers exist in my domain.
          >
          > I've tried using get MBeanHome, but in order to get that I must know the location of the admin server.
          >
          > I'd like to be able to discover from within my program the host name and port of the admin server,and then from there to be able to discover the managed servers and clusters that are running and on what machines/ ports they are running on.
          >
          > Is this possible.
          Its possible, but there are no public APIs for directly doing this. I
          guess you could try looking up the local server's MBean and navigating
          to the admin server's MBean from there.
          You could probably also deduce it from the system property
          weblogic.management.host that you would have set to boot the managed
          server.
          andy
          --

WLS: Several ManagedServer without clustering and same activities

Hi all,
I have a request for special solution for several ManagedServer without clustering and same activities (e.g. SOA or OSB).
In classic case, we have for example 1 AdminServer + 1 ManagedServer (SOA, or OSB). If we want to increase number of SOA-Managedserver, then we add other managed server in WLS-cluster.
In this case, we want to have several "Independent" ManagedServer with different port number and without cluaster but in same domain.
In addition, because we don't want to impact any project in one managed server to other managed server, we need to define different URL:ports for administration: For example: OSB has following URL:
http://localhost:7001/sbconsole
Is it possible to define other ports for other OSB-managed server? e.g. http://localhost:7003/sbconsole, http://localhost:7004/sbconsole
I would like to know, if any experience is available regarding this matter.
Thanks inadvance,
Moh

Hi Moh
1. There are few things that should be clear about the Weblogic Domain and Weblogic Cluster Architecture.
2. Any Weblogic Domain whether its Clustered or Non Clustered will have ONLY ONE Single AdminServer. You CANNOT have more than one AdminServer. Now for Cluster, you can have "n" number of Managed Servers and "n" number of Clusters. Each Cluster is just like a logical grouping of some managed servers. BUT main thing is, if you want to have High Availability architecture to support load balancing, fail over etc, you should and must have a Cluster with managed servers. And expose this Clustered Weblogic Servers into some sort of load balancer like Apace WebServer. Then expose single Apache Web Server URL (host, port + app url) to outside world. General practice is for HA architecture, you do not expose individual managed servers.
3. So coming to your requirement, you can have "n" number of managed servers. And each managed server can deploy their own specific application. And these managed servers naturally will have different port numbers, if they are all on the same physical box. If they are on different boxes, there is no clash of port numbers. Then in front end apache web server, check for each in coming request url and according direct that to appropriate backend weblogic server. This is good but you will NOT get any HA features going in this way. Instead of exposing individual managed servers, I would recommend just create a cluster for each one of them. And expose cluster. For now each cluster can have only 1 manged severs. Later on you can add more also. This gives you HA features. Something like this for example:
Domain = Single Domain
AdminServer = 1 AdminServer only. Not possible more then one.
ManagedServers = 4 (MS1, MS2, MS3, MS4)
Cluster1 = MS1, MS2 -> Deploy App1
Cluster2 = MS3 -> Deploy App2
Cluster3 = MS4 -> Deploy App3
Have a SINGLE Apache WebServer or any other Hard ware load balancer (Apache is free and widely used). Expose this host, port to outside world or actual users (outside or inside). In Apache httpd.conf file, configure like 3 settings, to check for incoming urls and redirect to back end cluster 1 or 2 or 3. Refer docs for full details.
Requests coming to Apache WebServer can use incoming url pattern and pass the request to appropriate backend cluster
http://apachehost:apachport/myApp1 -> Redirect to Cluster1
http://apachehost:apachport/myApp2 -> Redirect to Cluster2
http://apachehost:apachport/myApp3 -> Redirect to Cluster3
Now this gives you full flexibility to add or remove more servers from any of above Clusters. Even if you have single managed server, try to put that into cluster and expose the cluster.
4. Now comes the Adminstration applications like console, sbconsole, em (Enterprise Manager for SOA), cs (Content Server for ECM) etc. All these are deployed only to AdminServer and it makes sense also. Say in above architecture only AdminServer can have visibility to all the managed servers and clusters. Each managed server may not know about the others. Anyhow, the point is, for any Domain you will have only 1 AdminServer and most of the adminstration applications are deployed only to AdminServer. This means literally you will have just one url to control all the applications across all the clusters like http://adminhost:adminport/sbconsole. I am not familiar with sbconole, but for em I am sure its only targetted to admin server. Now, if you manually target these apps to cluster, not sure if this works also. Mostly it may not.
Also, admin urls are not exposed to any users. Only Adminstrators can access them. You can refine some rules like have very few admins with full privileges. Some can do only deployments, some can do only monitoring (read only access) etc.
Thanks
Ravi Jegga

Error while starting managed servers in a cluster

Hi,
          I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
          I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
          The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
          Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
          Can someone please tell me if I've missed something? I'd appreciated any help with this.
          Thanks
          Ameeth
          <Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
          .>
          <Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
          <Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
          r HTTP from Reactor-1.
          java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
          at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
          at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
          at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
          ketFactory;I)V(HttpClient.java:128)
          at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
          Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
          at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
          at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
          at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
          at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
          at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
          at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
          at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
          at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
          >
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
          ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
          emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
          icates with a full strength (domestic) license.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
          :\bea\weblogic81\server\lib\DemoTrust.jks.>
          <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
          :\bea\JROCKI~1\jre\lib\security\cacerts.>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
          7002, ip address 127.0.0.1>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
          ip address 127.0.0.1>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
          ain "ReactorAdminServer" running in Development Mode>
          <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
          <Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
          <Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
          r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
          actor-1.
          java.io.IOException: Reference to server no longer exists.
          Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
          n for this error.
          at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
          11)
          at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
          at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
          at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
          at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
          at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
          at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
          at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
          at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
          at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
          at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)

make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?

Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

Hi ,
In SCOM 2012 R2 console if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager servers have agent builds of 6.1.7221.49
Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
Thanks in advance
Bharath

Hi,
SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
you upgrade Service Manager so this is all expected and It´s as it should be :)
Regards,
Daniel
IT Consultant at Viridis IT

Weblogic.Admin command for stopping all Managed Servers in cluster

Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultant

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Need recommendation - iis with two physical servers and clusters

Hello,
I was hoping to get a recommendation/opinion or two on the configuration I've inherited. I'm looking
at the following configuration using weblogic 8.1 sp4 server (to be upgraded to sp6) running on two physical machines:
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7001
ManagedServer2:7010
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:7001
ManagedServer4:7010
On MachineA: IIS Proxy Plugin with parameter in .ini file
WeblogicCluster: MachineA:7001, MachineA:7010, MachineB:7001,MachineB7010
Naturally, the IIS is acting as a round robin load balancer..
The domains were created using the wizard on both machines and basic domain template..
For proper failover to be taken advantage of, does something different need to be configured? Or is it fine?
And if so, does group replication have something to do with it?
Should either of the clusters be Managed Servers across physical machines?
or should this just be one cluster of 4 managed servers across two machines?
I really am not sure on any of this, even though i've read through much of the documentation for clustering..twice.
I should mention that there is only a .war file deployed with 4 connection pools and 4 Data Sources..No EJBs or JMS
Would really appreciate any feedback or opinions/advice..
Thanks

This is what I'd do
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7010
ManagedServer2:7020
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:8010
ManagedServer4:8020
I just changed the port numbers so they flow and have a pattern - 70* port numbers belong to cluster 1, 80* port numbers belong to cluster 2. No technical benefit apart from it makes it tidier in my opinion.
Port 9001 for the admin server is normally the domain wide admin port - you could be using that, so that's fine, but my admin server is running 7001.
You also only need one admin server per domain, this can run on MachineA
Replication groups are used to help WLS figure out where to place the secondary http session. It will try servers on a different machine/replication group first, if none available, it will create secondary on the same machine.
What you will end up with is a domain with 4 managed servers in it. The admin server will run on machineA, say using port 7001, each of the managed servers will contact the admin server to download it's config.
The cluster1 will contain 2 managed servers and the same for cluster2.
providing you have your cluster multicast addresses set up and the cluster is working, that should be all you need to do for the session failover.
There's some BEA sample code somewhere which will deploy a web-app and show which managed server you've attached to. If you find that and then connect through IIS, shut down the server that the JSP tells you, you should be able to see the session fail-over nicely.
Hope that helps,
Pete

Performance of Clustered Managed Servers

WLS 10.3.5 on Solaris10
we have the clustered weblogic10.3.5 domain with two managed servers, which a web app deployed.
we use proxy server (an ohs server) as the frontend host.
we tested for the app login, if both managed servers are started, the login takes about 2 mins.
however if only one managed server is started, the login only takes less 1/2 min.
There is no problem to support two managed servers in the ram and cpu on the server
Why?
where should we start to look into the issue?

Hi,
According to the info you sent, there are 71GB of swap area in use and 7GB of real memory free.
This is not conclusive, as we don't know what is in the swap area. It could be part or the entire JVM for your application. Also, we have to take into consideration shared memory.
I believe you are running many applications in that server, and possible multiple environments.
In order to avoid spending too much time investigating other config issues that might not exist, I think you should try to eliminate the swap to see if this is the issue. I believe that this could be the main issue, based on the info I have so far.
Would be possible for you to stop all or some of the applications running in that server? Then you should check the available RAM (make sure that there are at least 10GB available before starting both managed servers) and restart both managed servers which you have your application running.
Regarding the response times for the login, does it always take the same time to login? You mentioned about 30 seconds, this also seems very high to me. Are your discarding the first login after the server restart? Depending on which framework you are using, it might be interpreting some artifacts or compiling the JSPs in the first execution.
Regards,
Fabio Douek

Two Managed servers in the same apahce.

Hi,
I did not have too much experience with WLS, I have two manged servers which listened on diff port, and I tried to configure them in one apache instance..
do u know how to do it? I have tried this:
<Location /weblogic>
SetHandler weblogic-handler
PathTrim /weblogic
</Location>
<IfModule mod_weblogic.c>
MatchExpression app1 WebLogicHost=192.1.1.87|WebLogicPort=7100|Debug=ON
MatchExpression app2 WebLogicHost=192.1.1.87|WebLogicPort=7200|Debug=ON
</IfModule>
And got the following error:
[Mon Jun 23 15:43:41 2003] [error] CONFIG_ERROR [line 1309 of ap_proxy.cpp]: Neither 'WebLogicCluster' nor 'WebLogicHost' specified in parameters
My WLS: 7 sp2 and apache is 2.0.45.
Appreciate your advice...
Regards
Leo

You can have more number of soa servers in a SOA domain. You can create mutiple managed servers using config wizard. But when you create more than one soa servers, then all the servers should exist in the same cluster.
You can not have the soa servers outside the soa cluster.

Running BizTalk on multiple non-clustered servers. Potential serious issue

Hi,
I have just discovered what has potential to be a fairly large issue in our current BizTalk Architecture. We are running BizTalk Server 2006 R2 on 2 different servers, running Windows Server 2003 R2. These servers are NOT clustered. Instead, BizTalk is installed
to both, configured on 1 and then on the 2nd, they have joined the existing BizTalk environment. We have 1 host with 2 host-instances for say an Orchestration Host. (So 1 Orchestration Host and then 1 Orchestration Host Instance on each server), we also have
a host instance for Receive and Send on each server.
This is a problem that I have identified on an application currently in UAT:
We have a routine called 'Recovery Mode'. It doesn't matter what Recovery Mode is but what does matter is that only a single instance can go into recovery mode at the same time.
Consider this:
bool inRecovery;
while (isBroken) {
if (!inRecovery){
inRecovery = true;
// Recover
inRecovery = false;
else {
// Wait, recheck until not in recovery, or fixed.
Imagine an instance on server 1 needs to go into recovery, it first checks the inRecovery flag, gets returned false so goes into recovery, let's say this takes 5 minutes to complete. During this time, an instance on server 2 needs to go into recovery, checks
the flag, but the flag on server 2 has not been set to true.... Now I have 2 instances in Recovery...
My questions are:
1. Can I cluster 2 non-clustered servers? I'd need to upgrade from Windows Server 2003 R2 Standard to Enterprise is that possible? If so, Can I simply upgrade and cluster the servers or would I need to format the disks?
2. If no to number 1, where would you store the 'inRecovery' flag'? I can't store in a DB as there will be slight cross over where instance 2 might return false in my example just as instance 1 is writing unless I can lock it on write or something.
Some advice would be greatly appreciated.
Thanks
Rod

To answer your specific question:
1. Yes, but you would need to upgrade to at least Enterprise. Windows Server 2003 R2 Standard does not support clustering. IIRC, the upgrade from Standard to Enterprise is pretty easy, perhaps just a SKU change.
2. If you absolutely cannot upgrade Windows Server, then you'd have to store the state externally, such as SQL Server. There shouldn't be any concurrency issues if you do the check in the right sequence. Basically, begin a transaction, attempt
to UPDATE, return weather the UPDATE was successful, meaning that call grabbed the lock. If you check then update, yes, there is a miniscule chance both will return the same value but only one near-sumultaneous UPDATE will succeed.

Transactional Replication: Non-Clustered Indexes not copying.

Hello,
I set up replication on our servers at work to streamline some procedures we run daily/weekly on them.
This copies around 15 articles from two databases on the "Master" server to another server used for execution purposes. For the most part it was a pretty straight forward task and it seemed to work nicely; but I realised after some investigation that the
non-clustered indexes weren't copying over to the child server.
I set the non-clustered indexes property in the properties of the publishing articles to "True" and generated a new snapshot, this seemed to work, but I've come into work this morning to find the property has reset to "False" and I have no indexes on the
table again. Why is this happening and is there any way I can resolve the matter so the indexes are copied over concurrently?
Thanks in advance for your advice.
JB

I actually solved this.
You can use a post-replication SQL script to create the indexes. Whatever articles you're publishing open up the indexes drop down list of the article in object explorer, right-click on an index and hover over Script Index as, then Create-to, then click
New Query Window editor.
Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
Once you're done find a safe folder somewhere on your harddrive and save the SQL query as an .sql file with a sensible name.
Right click on the publication and goto properties. Click on the "Snapshot" tab, in there; there should be a section saying "Run additional scripts". Choose the browse button next to "After applying the Snapshot; execute this script:"
Navigate to your script file and choose it. Once done click ok and it'll prompt you that something has changed and if you'd like to generate a new snapshot, make sure you do or it won't work.
That's it, you'll find once the publication has bulk copied over the the subscriptions successfully there are non clustered indexes on the tables. Pretty simple!

Two managed servers in one apache.

Hi,
I do not have too much experience with WLS, now I have two or more managed servers,
each one run different apps, but I want to use the same apache server for the
Front End(proxy). How to do it? I have tried this:
in httpd.conf:
<Location /weblogic>
SetHandler weblogic-handler
PathTrim /weblogic
</Location>
<IfModule mod_weblogic.c>
MatchExpression abc WebLogicHost=192.1.1.2|WebLogicPort=7100|Debug=ON
MatchExpression xyz WebLogicHost=192.1.1.2|WebLogicPort=7200|Debug=ON
</IfModule>
And got the following error:
[Mon Jun 23 15:43:41 2003] [error] CONFIG_ERROR [line 1309 of ap_proxy.cpp]: Neither
'WebLogicCluster' nor 'WebLogicHost' specified in parameters
Any suggestion are welcome...
Thanks
Leo

Hi,
The SAP Business One workstations read the name of the license service to which they connect from the SLIC table in the SBO-Common database. All Company databases sharing an SBO-Common database use the same license file. In addition, several SBO-Common databases can direct to the same license service.
For more information please refer to:
[License Guide 2007A|https://service.sap.com/~sapidb/011000358700000359212007E.pdf]
hope it helps,
Regards,
Ladislav
SAP Business One Forum Team

Transaction span two WLS managed servers (non-clustering)

Similar Messages

Maybe you are looking for