Environment Failover

Dear Forte-users,
here is a tricky question.
I'm checking the Forte' functionality that allows you to put multiple
addresses in FORTE_NS_ADDRESS, so that a client can connect to an
alternative environment in case of failover.
I have deployed my application in two alternative environment, called
AEnv and BEnv respectively.
I've paid attention to deploy the application exactly in the same way in
the two environment, that is, with the same partition numbering, so that
my application is deployed correctly to the client.
I've started two environment manager:
start_nodemgr -e AEnv -fns srv1:5000 -fnd srv1Node
start_nodemgr -e BEnv -fns srv2:6000 -fnd srv2Node
onto two different machines.
I've set my client FORTE_NS_ADDRESS to srv1:5000;srv2:6000 so that when
srv1 crashes, my client "should" automatically connect to srv2.
My application consists of three partitions: a client partition and two
server partition. The two server partition are replicated for failover
and are distributed to two different logical nodes. In environment AEnv
the two logical nodes corrispond to two different machines, whilst in
Benv the two logical nodes are on the same physical machine.
The platforms in use are: PC client (Windows 95) and AIX servers.
After all these setup operations, I've started up with my work.
To simulate an hardware crash of srv1, I killed all Forte' processes
(ftexec and all nodemgr) while my application was running, then I made a
new request to a server partition.
What I espected from Forte' was that my application connected to the
alternative environment and an autostart of the server partitions were
made in order to satisfy my client request.
What happens instead is that I receive a DistributedAccessException and
I have to exit the application. If I then execute again the application,
this time Forte' correctly connects to BEnv and autostarts the server
partitions.
I've also tried to start manually the server partitions in BEnv from
econsole, but with the same result.
In order to understand this behaviour, I've set the trc:do:35 flag.
Reading the trace messages, I've seen that in the case of a new
execution of the application there is at a certain time an
"InitiateNsBind", a "ClientCreateEnvironment" and some
"RegisterPartition". When I read the trace messages generated in the
case of DistributedAccessException I noted that Forte' correctly
initiates a bind to BEnv, but after that there is a "Got NAMESERVERAVAIL
event" message and no "ClientCreateEnvironment" or "RegisterPartition"
messages.
So I think it tries to use old references in the new connected
environment.
Thanks in advance for reading till the end !
If anyone has any idea or opinion, please let me know.
Regards,
Cristina.

Thank you Don.
I know that I have to handle the exception in case of Transaction or
Session Duration and I handled in fact the DistributedAccessException. I
think my problem could be connected to what you said by the end:
Specifying multiple name server addresses in FORTE_NS_ADDRESS onlyapplies to initial startup by the client. If the primary name server can't
be found, the client will try the other addresses in FORTE_NS_ADDRESS.
Once the client is connected, it uses the environment search path for
failover.
because I haven't used the search path.
And
Fourth - have you "warmed up" the application by talking to all serviceobjects in all partitions? Doing this will ensure that the client has a
list of all service objects in all partitions, in all connected
environments.
Yes, my request to the server partition involves al Service Objects, so my
client has a list of all of them.
I will try setting the environment search path.
Greeting,
Cristina.
[email protected] il 02/09/97 18.16.19
Per: Cristina Tomacelli/CSI/IT
cc: [email protected]
Oggetto: Re: Environment Failover
Cristina,
I'm assuming that you have connected the two environments. Keep in mind,
when connecting environments, that one environment is the "master", and
others are "subordinates." Thus, if Aenv was the master environment, you
should connect Benv to it.
Secondly, have you set the environment search path? For example:
@AEnv:@BEnv
Third, unless you're using message dialog duration, you will either have to
catch the AbortException (for transaction duration,) or the
RemoteAccessException for session duration. If you receive either of these
events, you would have to retry your message.
Fourth - have you "warmed up" the application by talking to all service
objects in all partitions? Doing this will ensure that the client has a
list of all service objects in all partitions, in all connected
environments.
Specifying multiple name server addresses in FORTE_NS_ADDRESS only applies
to initial startup by the client. If the primary name server can't be
found, the client will try the other addresses in FORTE_NS_ADDRESS. Once
the client is connected, it uses the environment search path for failover.
Hope this helps,
Don
At 04:34 PM 9/1/97 +0100, Cristina Tomacelli wrote:
Dear Forte-users,
here is a tricky question.
I'm checking the Forte' functionality that allows you to put multiple
addresses in FORTE_NS_ADDRESS, so that a client can connect to an
alternative environment in case of failover.
I have deployed my application in two alternative environment, called
AEnv and BEnv respectively.
I've paid attention to deploy the application exactly in the same way in
the two environment, that is, with the same partition numbering, so that
my application is deployed correctly to the client.
I've started two environment manager:
start_nodemgr -e AEnv -fns srv1:5000 -fnd srv1Node
start_nodemgr -e BEnv -fns srv2:6000 -fnd srv2Node
onto two different machines.
I've set my client FORTE_NS_ADDRESS to srv1:5000;srv2:6000 so that when
srv1 crashes, my client "should" automatically connect to srv2.
My application consists of three partitions: a client partition and two
server partition. The two server partition are replicated for failover
and are distributed to two different logical nodes. In environment AEnv
the two logical nodes corrispond to two different machines, whilst in
Benv the two logical nodes are on the same physical machine.
The platforms in use are: PC client (Windows 95) and AIX servers.
After all these setup operations, I've started up with my work.
To simulate an hardware crash of srv1, I killed all Forte' processes
(ftexec and all nodemgr) while my application was running, then I made a
new request to a server partition.
What I espected from Forte' was that my application connected to the
alternative environment and an autostart of the server partitions were
made in order to satisfy my client request.
What happens instead is that I receive a DistributedAccessException and
I have to exit the application. If I then execute again the application,
this time Forte' correctly connects to BEnv and autostarts the server
partitions.
I've also tried to start manually the server partitions in BEnv from
econsole, but with the same result.
In order to understand this behaviour, I've set the trc:do:35 flag.
Reading the trace messages, I've seen that in the case of a new
execution of the application there is at a certain time an
"InitiateNsBind", a "ClientCreateEnvironment" and some
"RegisterPartition". When I read the trace messages generated in the
case of DistributedAccessException I noted that Forte' correctly
initiates a bind to BEnv, but after that there is a "Got NAMESERVERAVAIL
event" message and no "ClientCreateEnvironment" or "RegisterPartition"
messages.
So I think it tries to use old references in the new connected
environment.
Thanks in advance for reading till the end !
If anyone has any idea or opinion, please let me know.
Regards,
Cristina.

Similar Messages

Named Anchored Obj-Environment Failover

Hi to all,
We connect from EnvA to EnvB giving the user directory parameter as / and
set the Environment Search Path
as EnvA:EnvB. From both environments we start and register
'/glob/obj1' named anchored objects with the same name.
From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
EnvB. And then we restart EnvA partition. We restart/rebind the client and
try to use object. We see that it is using the EnvB object.
Although we started the primary environment object again.
It is not using the search path. Once we shutdown secondary environment
it starts using primary environment object.
When we try to use relative path when we are binding the object
First parameter ('glob/obj1') No first slash. Trying 3rd parameter
for bind function or just using environment search path, Is is not able to
find the object. From nsls command I figured out that
under the root directory
/forte/UUID of ENVA/node
/site
/UUID of ENVB
/glob/obj1
names are available. When we use relative path (without slash)
is it trying to find /glob/obj1 under the /forte/UUID of ENVA
but we are registering the name under the root.
What is the reason of this odd behaviour or is this a bug?
Any answer will be appreciated,

Hi Juliesmiley,
According to your description, I recommend you check the conditions required for an automatic failover.
• Primary replica and secondary replica are both configured for syschronous-commit mode and set to AUTOMATIC failover.
• All availability databases that are defined in the availability group must be in a SYNCHRONIZED state between the primary replica and the secondary replica.
• The Windows Server Failover Clustering (WSFC) cluster has quorum.
• The primary replica has become unavailable.
For more information, please review the following articles.
Failover and Failover Modes (AlwaysOn Availability Groups)
Troubleshooting automatic failover problems in SQL Server 2012 AlwaysOn environments
Thanks,
Lydia Zhang

RE: Problems setting up environment failover SOLVED.

Kamran:
Solved the problem.
You know what was causing the problem ? The way I was copying files to
the destination environment. Yes, I was copying the files to vithar from
kronos in ASCII mode, which in turn modified the header information for
each file and Forte could not interpret them. Thanks to Martin who
found out this, and we copied the entire appdist dir structure again in
binary mode RE-INSTALLED all and now every thing looks great.
Thank you very much Kamran for your quick responses !
Thiru.
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Kamran:
Solved the problem.
You know what was causing the problem ? The way I was copying files to
the destination environment. Yes, I was copying the files to vithar from
kronos in ASCII mode, which in turn modified the header information for
each file and Forte could not interpret them. Thanks to Martin who
found out this, and we copied the entire appdist dir structure again in
binary mode RE-INSTALLED all and now every thing looks great.
Thank you very much Kamran for your quick responses !
Thiru.
Get Your Private, Free Email at http://www.hotmail.com
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Multiple shared services installs in the same environment?

In IOP 11.1.2 and beyond, shared services handles user authentication, to take advantage of Active Directory.
Can you install EPM shared services on 2 nodes in the same environment (failover in case one goes down)?
Is this possible or recommended?
Thank you.

I posted this message also in the Forum: Server & Storage Systems: Administration - General : Installation.
I'll also double-check the install documentation. A quick google of "EPM Shared Services" and some choice keywords revealed a link to this:
http://www.oracle.com/technetwork/middleware/bi-foundation/epm-hss-active-active-clusters-wp-1-132647.pdf
Note that one of the instructions in the active-active-clusters white paper is to install shared services on two nodes, to prevent a single point of failure.
This location http://www.oracle.com/technetwork/middleware/bi-foundation includes EPM DR instructions.
Highly recommended reading.
I apologize to the group for wasting the bandwidth on this question.
Thank you.

Apache and cluster and failover

          Hi All,
          I have a quick question. I am running 2 WLS 5.1 sp6 app servers
          in clustered mode (on solaris 7) using Apache 1.3.12 (also Solaris),
          and the weblogic proxy. Everything is working fine, and failover
          works correctly if one of the servers crashes.
          My problem is when the primary server for a session is correctly
          shut down. In my environment failover does not work in this situation.
          In the case that the server is shut down correctly, should failover
          occur? I would think that all sessions that are on the server
          being shut down would be transferred to the secondary server...
          is this a bug in weblogic? Or am I just wrong?
          Thanks again


          "Cameron Purdy" <[email protected]> wrote:
          >Some OS's combined with some WL releases will failover
          >on graceful
          >shut-down. Sometimes you just have to kill -9 or close
          >the port to get
          >failover to work.
          >
          >--That is very good information. Thank you. I do see the failover
          working correctly when I have 2 NT WLS app servers and a Solaris
          Apache web server. The problem occurs when I have 2 Solaris app
          servers and the Solaris Apache web server. does this sound familiar?
          >Cameron Purdy
          >Tangosol, Inc.
          >http://www.tangosol.com
          >+1.617.623.5782
          >WebLogic Consulting Available
          >
          >
          >"Nick Barbato" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >> Hi All,
          >>
          >> I have a quick question. I am running 2 WLS 5.1 sp6
          >app servers
          >> in clustered mode (on solaris 7) using Apache 1.3.12
          >(also Solaris),
          >> and the weblogic proxy. Everything is working fine,
          >and failover
          >> works correctly if one of the servers crashes.
          >>
          >> My problem is when the primary server for a session
          >is correctly
          >> shut down. In my environment failover does not work
          >in this situation.
          >> In the case that the server is shut down correctly,
          >should failover
          >> occur? I would think that all sessions that are on
          >the server
          >> being shut down would be transferred to the secondary
          >server...
          >> is this a bug in weblogic? Or am I just wrong?
          >>
          >> Thanks again
          >
          >

RE: (forte-users) Named Anchored Obj-EnvironmentFailover

I did some playing around with this stuff as well. I can tell you a few
things.
1) The search path option of connected environments only works for SO's, not
for named anchors.
2) When EnvA creates a directory "/glob", which contains object "obj1", then
EnvA owns directory "/glob". Even after restarting environments. If EnvB
tries to add a subdirectory to "/glob" or inserts its own objects into this
path, then the situation becomes unstable. It doesn't immediately produce an
error, but things go wrong anyway. Is this a bug or expected behaviour? I
don't know. I just learned not to do this. Every environment must place it's
named anchors in it's own tree. Directories can't be shared.
3) I think the relative name "glob/obj1" should work, but only if you set
the ObjectLocationMgr to start looking at the root. Default, it will start
looking in it's own environment basepath. But I don't have any experience
with this.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Master Programmer [mailto:masterprghotmail.com]
Sent: Monday, January 08, 2001 11:13 PM
To: forte-userslists.xpedior.com
Subject: (forte-users) Named Anchored Obj-Environment Failover
Hi to all,
We connect from EnvA to EnvB giving the user directory parameter as / and
set the Environment Search Path
as EnvA:EnvB. From both environments we start and register
'/glob/obj1' named anchored objects with the same name.
From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
EnvB. And then we restart EnvA partition. We restart/rebind the client and
try to use object. We see that it is using the EnvB object.
Although we started the primary environment object again.
It is not using the search path. Once we shutdown secondary environment
it starts using primary environment object.
When we try to use relative path when we are binding the object
First parameter ('glob/obj1') No first slash. Trying 3rd parameter
for bind function or just using environment search path, Is is not able to
find the object. From nsls command I figured out that
under the root directory
/forte/UUID of ENVA/node
/site
/UUID of ENVB
/glob/obj1
names are available. When we use relative path (without slash)
is it trying to find /glob/obj1 under the /forte/UUID of ENVA
but we are registering the name under the root.
What is the reason of this odd behaviour or is this a bug?
Any answer will be appreciated,
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

I did some playing around with this stuff as well. I can tell you a few
things.
1) The search path option of connected environments only works for SO's, not
for named anchors.
2) When EnvA creates a directory "/glob", which contains object "obj1", then
EnvA owns directory "/glob". Even after restarting environments. If EnvB
tries to add a subdirectory to "/glob" or inserts its own objects into this
path, then the situation becomes unstable. It doesn't immediately produce an
error, but things go wrong anyway. Is this a bug or expected behaviour? I
don't know. I just learned not to do this. Every environment must place it's
named anchors in it's own tree. Directories can't be shared.
3) I think the relative name "glob/obj1" should work, but only if you set
the ObjectLocationMgr to start looking at the root. Default, it will start
looking in it's own environment basepath. But I don't have any experience
with this.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Master Programmer [mailto:masterprghotmail.com]
Sent: Monday, January 08, 2001 11:13 PM
To: forte-userslists.xpedior.com
Subject: (forte-users) Named Anchored Obj-Environment Failover
Hi to all,
We connect from EnvA to EnvB giving the user directory parameter as / and
set the Environment Search Path
as EnvA:EnvB. From both environments we start and register
'/glob/obj1' named anchored objects with the same name.
From a client we connect to EnvA and bind to'/glob/obj1' when we shutdown EnvA partition it fails-over to
EnvB. And then we restart EnvA partition. We restart/rebind the client and
try to use object. We see that it is using the EnvB object.
Although we started the primary environment object again.
It is not using the search path. Once we shutdown secondary environment
it starts using primary environment object.
When we try to use relative path when we are binding the object
First parameter ('glob/obj1') No first slash. Trying 3rd parameter
for bind function or just using environment search path, Is is not able to
find the object. From nsls command I figured out that
under the root directory
/forte/UUID of ENVA/node
/site
/UUID of ENVB
/glob/obj1
names are available. When we use relative path (without slash)
is it trying to find /glob/obj1 under the /forte/UUID of ENVA
but we are registering the name under the root.
What is the reason of this odd behaviour or is this a bug?
Any answer will be appreciated,
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Forte/Visibroker/C++ question

I am trying to have a C++ client (MSVC++ 5.0) communicate via Visibroker
(3.2) with a Forte Service Object (3.0.G.2) and have had some success.
I have successfully received a sequence (array) of TextData from Forte,
but am having problems with retrieving strings returned from a method
call which returns a sequence of objects.
Here's the scenario:
The Forte service object is called 'InfoSO' whose service object base
class is 'InfoService'. The class InfoService has a method 'getNodes'
whose return type is 'Array of Node'. Upon invoking this method, an
array consisting of one 'Node' whose attribute 'mName' is set to 'Node1'
is returned. When I try to invoke Node's 'getName()' accessor, I get
the following Visibroker exception:
Exception: CORBA::OBJECT_NOT_EXIST
Minor: 0
Completion Status: NO
I have included the Forte wex and C++ files below. In order to compile
the C++ file, I have commented out the line from the C++ header file
(corba1_c.h) generated after invoking idl2cpp as follows:
//typedef CORBA::Long int;
Has anyone had a similar situation and found a solution?
Thanks for any suggestions.
==================== Forte wex file =====================
begin TOOL CompFramework;
includes Framework;
HAS PROPERTY IsLibrary = FALSE;
-- START FORWARD CLASS DECLARATIONS
forward Node;
-- END FORWARD CLASS DECLARATIONS
-- START FORWARD CURSOR DECLARATIONS
-- END FORWARD CURSOR DECLARATIONS
-- START CONSTANT DEFINITIONS
-- END CONSTANT DEFINITIONS
-- START C DATA TYPE DEFINITIONS
-- END C DATA TYPE DEFINITIONS
-- START CLASS DEFINITIONS
class Node inherits from Framework.Object
has public attribute mName: Framework.TextData;
has public method getName: Framework.string;
has public method Init;
has public method setName(input Name: Framework.string);
has property
shared=(allow=off, override=on);
transactional=(allow=off, override=on);
monitored=(allow=off, override=on);
distributed=(allow=on, override=on, default=off);
end class;
-- END CLASS DEFINITIONS
-- START SERVICE OBJECT DEFINITIONS
-- END SERVICE OBJECT DEFINITIONS
-- START CURSOR DEFINITIONS
-- END CURSOR DEFINITIONS
-- START TYPEDEF DEFINITIONS
-- END TYPEDEF DEFINITIONS
-- START METHOD DEFINITIONS
method Node.getName: Framework.string
begin
return mName.Clone(deep=TRUE).Value;
end method;
method Node.Init
begin
super.Init();
mName = new();
end method;
method Node.setName(input Name: Framework.string)
begin
mName = TextData(Name).Clone(deep=TRUE);
end method;
-- END METHOD DEFINITIONS
HAS PROPERTY
CompatibilityLevel = 0;
ProjectType = APPLICATION;
Restricted = FALSE;
MultiThreaded = TRUE;
Internal = FALSE;
LibraryName = 'compfram';
end CompFramework;
begin TOOL Server;
includes CompFramework;
includes Framework;
HAS PROPERTY IsLibrary = FALSE;
-- START FORWARD CLASS DECLARATIONS
forward InfoService;
forward StartUp;
-- END FORWARD CLASS DECLARATIONS
-- START FORWARD CURSOR DECLARATIONS
-- END FORWARD CURSOR DECLARATIONS
-- START CONSTANT DEFINITIONS
-- END CONSTANT DEFINITIONS
-- START C DATA TYPE DEFINITIONS
-- END C DATA TYPE DEFINITIONS
-- START CLASS DEFINITIONS
class InfoService inherits from Framework.Object
has public method getNodes: Framework.Array of CompFramework.Node;
has public method Init;
has property
shared=(allow=off, override=on);
transactional=(allow=off, override=on);
monitored=(allow=off, override=on);
distributed=(allow=on, override=on, default=off);
end class;
class StartUp inherits from Framework.Object
has public method Init;
has public method StartMethod;
has property
shared=(allow=off, override=on);
transactional=(allow=off, override=on);
monitored=(allow=off, override=on);
distributed=(allow=off, override=on);
end class;
-- END CLASS DEFINITIONS
-- START SERVICE OBJECT DEFINITIONS
service InfoSO : Server.InfoService = (DialogDuration = MESSAGE,
Visibility = environment,
FailOver = FALSE,
LoadBalance = TRUE) HAS PROPERTY extended = (UUID =
'8A0E2800-387A-11D2-
BFA0-DEA162A6AA77');
-- END SERVICE OBJECT DEFINITIONS
-- START CURSOR DEFINITIONS
-- END CURSOR DEFINITIONS
-- START TYPEDEF DEFINITIONS
-- END TYPEDEF DEFINITIONS
-- START METHOD DEFINITIONS
method InfoService.getNodes: Framework.Array of CompFramework.Node
begin
Nodes: Array of Node = new();
aNode: Node = new();
aNode.setName('Node1');
Nodes.AppendRow(aNode);
return Nodes;
end method;
method InfoService.Init
begin
super.Init();
end method;
method StartUp.Init
begin
super.Init();
end method;
method StartUp.StartMethod
begin
a : InfoService = InfoSO;
end method;
-- END METHOD DEFINITIONS
HAS PROPERTY
CompatibilityLevel = 0;
ProjectType = APPLICATION;
Restricted = FALSE;
MultiThreaded = TRUE;
Internal = FALSE;
LibraryName = 'server';
StartingMethod = (class = StartUp, method = StartMethod);
end Server;
====================== C++ file ===============================
#include <fstream.h>
#include <iostream>
#include <string>
#include "corba1_c.h"
int
main(int argc, char** argv)
try
CORBA::ORB_var orb = CORBA::ORB_init(argc, argv);
ifstream from("c:\\forte\\etc\\iiopior\\server.ior");
char ch;
std::string ior_str;
while (from.get(ch))
ior_str += ch;
from.close();
CORBA::Object_var obj;
obj = orb->string_to_object( ior_str.c_str() );
Server::InfoService_var InfoSO;
InfoSO = Server::InfoService::_narrow(obj);
CompFramework::sequence_Node* nodes;
nodes = InfoSO->getNodes();
for (CORBA::ULong i=0; i<nodes->length(); i++)
cout << (*nodes)->getName() << endl;
catch(const CORBA::Exception& e)
cerr << e << endl;
return 1;
return 0;
======================== end of files ===================
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

I just knocked up a quick C console "Hello World" program, including
ddeml.h, and got compilation errors.
Using borlands free C++ 5.5 compiler.
I don't think you're supposed to include that include file directly.
I done a search of the standard system include files, and it's already imported in windows.h.
When I include windows.h instead of ddeml.h, it compiles and runs.
I had to force C++ compilation though.
Compile line to compile:
bcc32.exe -P test.c
The -P forces a C++ compile on t C source.
Within my directory, I had a bcc32.cfg file, with my custom compiler switches too... This file contained the following, which can normally be specified on the command line. ( the paths will be different for you )
-I"d:\Compilers\Bcc55\include;d:\Compilers\Borland\CBuilder3\Include\VCL;d:\Compilers\jdk1.3.1_01\include;d:\Compilers\jdk1.3.1_01\include\win32"
-L"d:\Compilers\Bcc55\lib"
-3
-a8
-tWC
-RT
regards,
Owen

Dynamic access to available distributed objects.

What I want is a method called, say, PingAllServices().
This method will attempt to communicate with every service
object "visible" to it. Is Forte capable of providing me
with a list of service objects (remote and local) "visible" to me?
I would also need the ability to attempt to "connect" to this
service object.
The advantages are:
1) Won't have to change code if I change my partition scheme.
2) I only have one version of the method which can be invoked
from any partition.
3) Service objects are not hard coded.
(Avoids bugs where someone has added a service object,
but not updated the method)
4) Perfect for "warm starting" all of my partitions in
a connected environment/failover scenario
5) Startup order of partitions is not an issue. (I could
code to "wait" for all "visible" service objects to
become available).
Mark Sundsten
Unified Information, Inc.
425-814-4012

For simple reflection, I find Statement and Expression of package java.beans handy, but it does have its limitations. Try it:
public class CrappyBean {
    private int value;
    public void setValue(int value) {
        this.value = value;
    public int getValue() {
        return value;
import java.beans.Statement;
import java.beans.Expression;
public class StatementUse {
    public static void main(String[] args) throws Exception {
        CrappyBean object = new CrappyBean();
        Statement setter = new Statement(object, "setValue", new Object[]{17});
        Expression getter = new Expression(object, "getValue", null);
        setter.execute();
        System.out.println(getter.getValue());
}

How to keep track of EJBs in case of failover under clustered environment?

Does anybody know what happens with a stateless session EJB in
weblogic 5.1 under clustered environment, in case of a failover (if
one of computers dies), the one, which keeps that ejb in a pool?
Does that EJB automatically go to the state "does not exist"?
Is method ejbRemove() then called on that EJB?
Or is it still in the "method-ready pool" state? Without ejbCreate()
method being called on this EJB?
Or does it disappear completely without those methods being called on
this EJB?
I need to organize some kind of tracking for those EJBs, and it is
critically important for me to understand what exactly methods are
called on those EJBs.
I saw this, but it does not answer my question:
Clustered EJB
All EJBs are clusterable. If an EJB is deployed on multiple servers in
the cluster, each of these servers will be able to host instances of
the bean. This does not necessarily mean, however, that the bean
instances are clustered.
EJB Homes
All bean homes are clusterable. When a bean is deployed on a server,
its home is bound into the cluster-wide naming service. Because homes
are clusterable, each server can bind an instance of the home under
the same name. When a client looks up this home, it gets a
replica-aware stub that has a reference to the home on each server
that deployed the bean. When create() or find() is called, the
replica-aware stub routes the call to one of the replicas. The home
replica that receives the finds or creates an instance of the bean on
its server.
Stateless EJBs
When a home creates a stateless bean, it returns a replica-aware stub
that can route to any server on which the bean is deployed. Because a
stateless bean holds no state on behalf of the client, the stub is
free to route any call to any server that hosts the bean. Also,
because the bean is clustered, the stub can automatically fail over in
the event of a failure. The stub does not automatically treat the bean
as idempotent, so it will not recover automatically from all failures.
If the bean has been written with idempotent methods, this can be
noted in the deployment descriptor and automatic fail-over will be
enabled in all cases.
Thanks

Check out Java's support for udo/redo: [http://java.sun.com/javase/6/docs/api/javax/swing/undo/package-summary.html]
Also, google the "Memento Pattern".
You don't have to make copies of objects, just maintain commands the can undo and redo your program's state.

DHCP Failover in Windows 2008 R2 and Windows 2012 R2 Environment

Hi Everyone,
We are trying to implement DHCP failover in our environment. Our IT Infrastructure consists of 4 – windows server 2008 R2 servers and 7 – Windows Server 2012 servers; 1 Main Office with 2 – DC’s and 9 branch/remote offices with one DNS server in every remote
office. All the DNS servers have 2 scopes defined on them for VOICE and Data with different Subnets.
What would be the best method to implement failover in 2008 R2 – Windows Failover Cluster or Split scope? And how to implement DHCP Failover in Windows Server 2012 R2?
Please let me know if you need more information.
Thank you for your help!
-kN

Hi,
if you can choose between 2008 R2 and 2012 R2 than go with 2012 R2 it is easy to create a DHCP failover there. Actually that is one of the new features of Windows 2012.
With Server 2012 you setup your fist DHCP server with the scopes you want to setup. Than you install the second 2012 server with DHCP role and authorized. If you have done this you going back to your first server, where you already configured your scopes.
Now right click onto the scope you want to setup for failover and select 'Configure Failover'. You can than set it up as kind of split scope (Load balance Mode) or as real fail over setup (Hot Standby). In Load balance Mode you can configure the balance of
IP addresses between the both servers, like primary has 60% IP addresses and secondary has 40%.
With Server 2008 R2 the easiest configuration is split scope. But here it depends how many IP leases you will max have and if you can absorb if one of the server is going down. Lets say you have 50 DHCP leases max, than sure, set it up as split scope. But
if you have 200 DHCP clients, than I would go with failover cluster. At the end it depends on your environment.
Sven

Load balancing, failover and fallback in Non-Clustered WebLogic environment

hi,
Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
Any help appreciated.
Thanks.
Best regards,
Bala

hi,
Has anyone implemented WebLogic 10.3.3 (or 10.3.4) in a Non-Clustered environment, but also got load balancing, failover and fallback work?
We were successful in getting failover working using t3://server1:7001,server2:7002 provider URL, but not load balancing or fallback.
The fallback is working when it was connecting to server2 and if we kill server2, then it switches to server1, but not when server2 is still running while server1 comes back.
All we need to find a way to enforce fallback to primary site, even if secondary which the client connected is still up and running and primary site comes back.
Any help appreciated.
Thanks.
Best regards,
Bala

Project Server 2010 failover environment with Database SQL Mirroring

Hello,
We have prod and failover environment. Failover environment created by using farm backup and restore of prod.
my question is : Can we do SQL Mirroring (from prod to failover) of 5 databases (4 PS databases and content db) to keep both the environment in sync. Will this process work in the case of Project
Server 2010. i am in doubt due to timestamp and GUID in config DB.
Also will this process is supportable.
Any help much appreciated.
Thanks

Hello MOhit2020,
I haven't done this type of failover, but I think you would need to setup all your SharePoint and project databases to use a SQL Alias to point to your production databases. When and if your production databases failed, you would update
your SQL Alias to point to the mirror location.
The other nice feature about having SQL Alias setup in SharePoint, is that in the future, if you switch to another SQL Server, the SQL alias makes it easier to handle.
Cheers!
Michael Wharton, MVP, MBA, PMP, MCT, MCTS, MCSD, MCSE+I, MCDBA
Website http://www.WhartonComputer.com
Blog http://MyProjectExpert.com contains my field notes and SQL queries

How to test failover of dataguard environment?

I would like to test failover (not switchover ) in dataguard environment.
How to achieve that?
Thanks.

Hello;
Happy to share my test notes :
http://www.visi.com/~mseberg/Data_Guard_Failover_Test_using_SQL.pdf
These oracle notes may also help :
Can We Use Manual SQL*PLUS Steps For (switchover,Failover,etc....), If DataGuard Broker Has Already Activated And GridControl Is Also Used? [ID 744396.1]
Oracle10g: Data Guard Switchover and Failover Best Practices [ID 387266.1]
Step by Step Guide on How To Reinstate Failed Primary Database into Physical Standby [ID 738642.1]
Best Regards
mseberg

Adding a failover server in Unity 7.0(2) messaging only environment

Were are using a single Unity 7.0(2) server (messaging only) with Exchange and the message store running on the same server. We want to introduce a failover server in the invironment.
I originalloy built the server using the "istallation Guide for Cisco Unity Release 5.x in a Voice Messaging Configuration with Microsoft Exchange (Without Failover)" instructions.
I have two questions:
Can I convert the existing server to a failover configuration with out having to rebuild it from scratch?
My next question is, since the documentation I'm reading states that the message store must be on the secondary server, is there a way to migrat the message store over?
Thank for any help.
Jim Lozano
SOCCCD District IT

Bradford,
Thanks for the reply and this looks like it might be my problem. Question though, I see there is an option in advanced settings tools to exclude return reciepts from voice mail stack but I do not see the registry key. Do I need both or will changing it in advanced tools be sufficient?
Thanks,
Glenn

Service not failover on RAC 11.2.0.3 environment

Hi
now i am testing how the 11.2.0.3 RAC will behave with Redhat 5.7.
then, i found the rac service will not failover to other node which added with "-r" available option
i have made service with this command
"srvctl add service -d xxxdb -s srv_p01 -r xxxdb1 -a xxxdb2 -y automatic -f"
xxxdb means database name, xxxdb1 and xxxdb2 are the instance on each nodes.
in my thought it will be that when prefferd xxxdb1 stopped accidentaly, the service "srv_p01" failover to availabled xxxdb2 instance
but when i stop the xxxdb1 instance with "srvctl stop instance" command, this service won't failover...
**following is the Nomal status
ora.xxxdb.db
1 ONLINE ONLINE node01 Open
2 ONLINE ONLINE node02 Open
ora.xxxdb.srv_p01.svc
1 ONLINE ONLINE node01
**here is the status when i stop the instance on node01
ora.xxxdb.db
1 OFFLINE OFFLINE Instance Shutdown
2 ONLINE ONLINE 02 Open
ora.xxxdb.srv_p01.svc
1 ONLINE OFFLINE
now the point of my question;
1. when instance down, the service which running on downed instance will failover to other node which registered as "availbale"?
the incident i met is normal activity?
2. if this activity is normal, why i add service with "available" option?
3. i want to know when the service failover to available node?
**here is the status i think it should be when instance down..
ora.xxxdb.db
1 OFFLINE OFFLINE Instance Shutdown
2 ONLINE ONLINE 02 Open
ora.xxxdb.srv_p01.svc
1 ONLINE ONLINE node02
Anyone pls answer my question! pls..
Thanks,
Edited by: 937532 on 2012/05/30 22:29

but when i stop the xxxdb1 instance with "srvctl stop instance" command, this service won't failover...yes it won't like 10g,crash the node or instance or do shutdown abort on instance in 11g and see service will failover.
1. when instance down, the service which running on downed instance will failover to other node which registered as "availbale"? the incident i met is normal >activity?when instance aborted the service will failover to available instance which you're define on -a, and this service will be available to accept new connection.
2. if this activity is normal, why i add service with "available" option?explain above.
3. i want to know when the service failover to available node?when instance,node crash.

Environment Failover

Similar Messages

Maybe you are looking for