本文整理汇总了C++中CMultiXAppMsg::Keep方法的典型用法代码示例。如果您正苦于以下问题:C++ CMultiXAppMsg::Keep方法的具体用法?C++ CMultiXAppMsg::Keep怎么用?C++ CMultiXAppMsg::Keep使用的例子?那么, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类CMultiXAppMsg
的用法示例。
在下文中一共展示了CMultiXAppMsg::Keep方法的6个代码示例,这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞,您的评价将有助于系统推荐出更棒的C++代码示例。
示例1:
void CISO8583AcquirerGatewayFEServerSession::OnNetworkManagementRequest(CMultiXAppMsg &Msg)
{
CISO8583Msg ISOMsg;
CISO8583Msg::TValidationError Error = ISOMsg.FromISO((const byte_t *)Msg.AppData(),Msg.AppDataSize());
if(Error != CISO8583Msg::NoError)
{
Msg.Reply(Error);
return;
}
/*
Since Network Management messages include the destination gateway ID, we use it to find the link associated with this gateway.
*/
int ReplyError = ErrUnableToForwardMsg;
CISO8583AcquirerGatewayFELink *Link = Owner()->FindReadyLink(ISOMsg.TransactionDestinationInstitutionIdentificationCode());
if(Link)
{
std::string MsgKey = ISOMsg.STAN() + ISOMsg.DateTimeLocal() + ISOMsg.TransactionOriginatorInstitutionIdentificationCode();
ReplyError = Link->Forward(Msg,MsgKey);
}
if(ReplyError == 0)
{
Msg.Keep();
} else
{
Msg.Reply(ReplyError);
}
}
示例2:
bool CMultiXWSStream::CallServiceNoWait(CMultiXAppMsg &Msg)
{
if(!IsRunning())
if(!Start())
return false;
CMultiXWSStreamEvent *Ev = new CMultiXWSStreamEvent(CMultiXWSStreamEvent::CallServiceFromMessage);
Msg.Keep();
Ev->m_MsgID = Msg.ID();
QueueEvent(Ev);
return true;
}
示例3:
void CISO8583AuthorizerServerSession::ForwardToIssuer(int CreditAccountAtIssuer,CMultiXAppMsg &Msg,CISO8583Msg &ISOMsg)
{
/*
we get here if we need someone else to authorize the request. In that case we need to forward the request to our Acquirer Gateway Front End.
To do that we need to forward it with a different message code, so MultiXTpm will not forward it back to us. The way we do it,
the message code change is by setting the MTI version field to CISO8583Msg::ISO8583_Private. When the message is received by our
Gateway process, it will revert back to CISO8583Msg::ISO8583_2_1993 and forward it on.
When we forward a request, we do not block for a response, when a response arrives, we get it thru
the event "OnDataReplyReceived". in order to be able to associate the response with the original msg,
we pass a pointer to the original message in the "Context" parameter of the "Send" function, and when
"OnDataReplyReceived" is called, we retrieve this pointer by using "SavedContext()" in the Original msg we sent.
Since MultiX automatically destroys messages it forwards to the application, we must call "Keep()" on
the received message, to prevent it from being destroyed, in that case, when the reply is received, we need
to destroy the original message ourselves.
When we play the role of an acquirer gateway, usualy get the request from the POS terminal, do validation required
and maybe modify some data, and then forward the message to the issuer gateway, in our case, the forward will be to a process
in our system, that will decide to which issuer to forward to, based on that, will use a specific connection to the spcific
issuer gateway.
*/
/*
Before we forward the request, we need to set 3 fields to identify the message as a one sent from this process :
BMP 11 - STAN,
BMP 12 - Times,
BMP 32 - Our Acquirer ID
BMP 42 - our account within the issuer
When we receive the response from the remote gateway/issuer, we must replace these fields again to the orignal values
that the sender set before sending the request to us
*/
ISOMsg.SetTimes(time(NULL));
ISOMsg.SetSTAN(Owner()->GetNextSTAN());
ISOMsg.SetAcquiringInstitutionIdentificationCode(Owner()->MyAcquirerID());
CISO8583ElementValue Value(CISO8583Utilities::ToString(CreditAccountAtIssuer),CISO8583ElementValue::ISO8583ElementTypeNumeric);
ISOMsg.SetCardAcceptorIdentificationCode(Value);
ISOMsg.ToISO();
if(Send(CISO8583Msg::VersionDependentMTI(CISO8583Msg::ISO8583_Private,Msg.MsgCode()),ISOMsg.ISOBuffer(),ISOMsg.ISOBufferSize(),CMultiXAppMsg::FlagNotifyAll,0,0,&Msg))
Msg.Keep();
else
Msg.Reply(ErrUnableToForwardMsg);
}
示例4:
void CMultiplexerServerFEServerSession::OnNewMsg(CMultiXAppMsg &Msg)
{
DebugPrint(1,"New Message Received\n");
int ReplyError = ErrUnableToForwardMsg;
CMultiplexerServerFELink *Link = Owner()->FindReadyLink(Msg.MsgCode());
if(Link)
{
ReplyError = Link->Forward(Msg);
}
if(ReplyError == 0)
{
Msg.Keep();
} else
{
Msg.Reply(ReplyError);
}
}
示例5: RemoteGatewayID
void CISO8583AcquirerGatewayFEServerSession::OnTransactionRequest(CMultiXAppMsg &Msg)
{
CISO8583Msg ISOMsg;
CISO8583Msg::TValidationError Error = ISOMsg.FromISO((const byte_t *)Msg.AppData(),Msg.AppDataSize());
if(Error != CISO8583Msg::NoError)
{
Msg.Reply(Error);
return;
}
if(Owner()->DebugLevel() >= 5)
{
std::string S;
ISOMsg.Dump(S);
DebugPrint(2,"New ISO 8583 Message\n%s\n",S.c_str());
}
/*
When we receive a transaction for forwarding, we have no indication within the message, to which gateway we should forward the message.
It is assumed that there is some mechanism to use the PAN and/or Track2 in order to decide to which gateway we should forward the request.
In this application, we do not use any logic to derive the Gateway ID from these details. We just use a stub routine that gets PAN
as input and returns the gateway ID of the issuer. Using the gateway ID, we look for a link that its RemoteGatewayID() is equal to
the value returned. If we find one and it is signed in, we forward the request to it, otherwise we reply with an error.
*/
int ReplyError = ErrUnableToForwardMsg;
std::string RemoteGatewayID = PANToGatewayID(ISOMsg.PAN());
CISO8583AcquirerGatewayFELink *Link = Owner()->FindReadyLink(RemoteGatewayID);
if(Link)
{
std::string MsgKey = ISOMsg.STAN() + ISOMsg.DateTimeLocal() + ISOMsg.AcquiringInstitutionIdentificationCode();
ReplyError = Link->Forward(Msg,MsgKey);
}
if(ReplyError == 0)
{
Msg.Keep();
} else
{
Msg.Reply(ReplyError);
}
}
示例6: if
//.........这里部分代码省略.........
{
Msg.Reply(CISO8583Msg::ExtraElementsFound);
return;
}
// check that we have Original Data Elements
if(ISOMsg.OriginalDataElements().Size() == 0)
{
Msg.Reply(CISO8583Msg::OriginalDataElementsIsMissing);
return;
}
// check that we have Authorizing Agent Institution Identification Code
if(ISOMsg.AuthorizingAgentInstitutionIdentificationCode().Size() == 0)
{
Msg.Reply(CISO8583Msg::AuthorizingAgentInstitutionIdentificationCodeIsMissing);
return;
}
// check that we have MAC, we do not check the values because we do not have the Keys
// in this implementation.
if(ISOMsg.MAC1() == "")
{
Msg.Reply(CISO8583Msg::MAC1IsMissing);
return;
}
/*
After we finished validating the request, we need to decide if we authorize locally or we forward it to
the issuer for authorization
*/
if(AuthorizeLocally(ISOMsg)) // in this example it is always true
{
// We create a new ISO Message
// we will decline this message
CISO8583Msg Rsp;
// We will Dup field from the original message and add/ change the ones that are relevant for the response
Rsp.SetMTI(CISO8583Msg::VersionDependentMTI(CISO8583Msg::ISO8583_2_1993,CISO8583Msg::MTIReversalMessageAdviceResponse)); // this is a response
Rsp.SetPAN(ISOMsg.PAN());
Rsp.SetProcessingCode(ISOMsg.ProcessingCode());
Rsp.SetTransactionAmount(ISOMsg.TransactionAmount());
Rsp.SetCardholderBillingAmount(ISOMsg.CardholderBillingAmount());
Rsp.SetTimes(time(NULL),true); // This will set transmission time
Rsp.SetDateTimeLocal(ISOMsg.DateTimeLocal());
Rsp.SetCardholderBillingConversionRate(ISOMsg.CardholderBillingConversionRate());
Rsp.SetSTAN(ISOMsg.STAN());
Rsp.SetAcquiringInstitutionIdentificationCode(ISOMsg.AcquiringInstitutionIdentificationCode());
Rsp.SetRRN(ISOMsg.RRN());
Rsp.SetActionCode(std::string("909")); // System Mulfunction
Rsp.SetTransactionCurrencyCode(ISOMsg.TransactionCurrencyCode());
Rsp.SetCardholderBillingCurrencyCode(ISOMsg.CardholderBillingCurrencyCode());
Rsp.SetSecurityRelatedControlInformation(std::string("00000007000001FFFF")); // this is a dummy value, real value should be set based on Keys.
Rsp.SetOriginalDataElements(ISOMsg.OriginalDataElements());
Rsp.SetMAC1(std::string("0123456789ABCDEF")); // dummy value, should be based on keys
CISO8583Msg::TValidationError Error = Rsp.ToISO();
if(Error != CISO8583Msg::NoError)
Throw();
// we are done preparing the response, we reply with an MTI = CISO8583Msg::MTIAuthorizationMessageResponse
// and the handling is complete.
Msg.Reply(Rsp.MTI(),Rsp.ISOBuffer(),Rsp.ISOBufferSize());
} else
{
/*
we get here if we need some external processing on behalf of this request, so we forward the request
with a different message code (so MultiXTpm will not forward it back to us). In this case we just set
the msg code to the same MTI but with CISO8583Msg::ISO8583_Private version (in MultiXTpm we must configure this message code !!!).
When we forward a request, we do not block for a response, when a response arrives, we get it thru
the event "OnDataReplyReceived". in order to be able to associate the response with the original msg,
we pass a pointer to the original message in the "Context" parameter of the "Send" function, and when
"OnDataReplyReceived" is called, we retrieve this pointer by using "SavedContext()" in the Original msg.
Since MultiX automatically destroys messages it forwards to the application, we must call "Keep()" on
the received message, to prevent it from being destroyed, in that case, when the reply is received, we need
to destroy the original message ourselves.
When we play the role of an acquirer gateway, we usualy get the request from the POS terminal, do validation required
and maybe modify some data, and then forward the message to the issuer gateway, in our case, the forward will be to a process
in our system, that will decide to which issuer to forward to, based on that, will use a specific connection to the spcific
issuer gateway.
*/
if(Owner()->MyAcquirerID().length() == 0)
Msg.Reply(ErrUnableToForwardMsg);
/*
Before we forward the request, we need to set 3 fields to identify the message as a one sent from this process :
BMP 11 - STAN,BMP 12 - Times, BMP 32 - Our Acquirer ID
When we receive the response from the remote gateway/issuer, we must replace these fields again to the orignal values
that the sender set before sending the request to us
*/
ISOMsg.SetTimes(time(NULL));
ISOMsg.SetSTAN(Owner()->GetNextSTAN());
ISOMsg.SetAcquiringInstitutionIdentificationCode(Owner()->MyAcquirerID());
ISOMsg.ToISO();
if(Send(CISO8583Msg::VersionDependentMTI(CISO8583Msg::ISO8583_Private,Msg.MsgCode()),ISOMsg.ISOBuffer(),ISOMsg.ISOBufferSize(),CMultiXAppMsg::FlagNotifyAll,0,0,&Msg))
Msg.Keep();
else
Msg.Reply(ErrUnableToForwardMsg);
}
}