Configure Network Enabler Fallback Processing (Multiple Sub-Domains)

Perform this task to configure Network Enabler to use non-default fallback processing on platforms that use sub-domain routing.

About this task

Procedure

Go to the ${MTX_CUSTOM_DIR} directory:
cd_custom_dir

Open the create_config.info file with a text editor and change the answer to the following questions to y:

Do you want to enable special handling of messages when a domain is unreachable?
Do you want to enable special handling of messages when a domain cannot be looked up?

(Optional) To ensure that traffic is still sent to Network Enablers when all processing pods are down, change the answer to the following create_config.info question. Enter a comma-separated list of SSNs for Network Enablers to always activate:
```
Network Enabler:What are the SSNs Network Enabler should always activate?
```
Save and close the file.
Run the configure_engine.py script as user mtx.

Configure how Network Enabler processes messages when it is unable to reach the sub-domain by answering the following create_config.info questions:

Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?
What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable
                                domain?
Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for an unreachable domain(y/n)? 
Do you want to send END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for an unreachable domain (y/n)?
What is the release cause to put in END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for an unreachable
                                        domain?
Do you want to send END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable domain (y/n)?
Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for an unreachable domain(y/n)? 
What is the release cause to put in END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for an unreachable
                                domain?
Do you want to suppress UDTS responses for other messages received for an unreachable domain (y/n)?
Do you want to use selective updates to determine the action to be taken on receipt of a message for an unreachable
                                        domain(y/n)?

Note: Some create_config.info questions depend on answers to earlier questions. For example, if you answer y to the question:

Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?
Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable domain (y/n)?

The next question asked is:

What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for an unreachable
                                domain?

If you answer n, the next question asked is:

Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for an unreachable domain(y/n)?

For more information, see the discussion about Network Enabler fallback processing configuration properties.

Configure how Network Enabler processes messages when it is unable to look up the sub-domain by answering the following create_config.info questions:

Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?
What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up?
Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?
Do you want to send END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for which the domain cannot be looked up(y/n)?
What is the release cause to put in END(ReleaseCall) on receipt of CONTINUE(ACR or ERBCSM) for which the domain cannot be looked up?
Do you want to send END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up(y/n)?
Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?
What is the release cause to put in END(ReleaseSMS) on receipt of BEGIN(InitialDPSMS) for which the domain cannot be looked up?
Do you want to suppress UDTS responses for other messages received for which the domain cannot be looked up(y/n)?
Do you want to use selective updates to determine the action to be taken on receipt of a message for which the domain cannot be looked up(y/n)?

Note: Some create_config.info questions depend on answers to earlier questions. For example, if you answer y to the question:

Do you want to send END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?

The next question asked is:

What is the release cause to put in END(ReleaseCall) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up?

If you answer n, the next question asked is:

Do you want to send END(Continue) on receipt of BEGIN(InitialDP) for which the domain cannot be looked up(y/n)?

For more information, see the discussion about Network Enabler fallback processing configuration properties.

If you answered y to the following question, configure selective updates on the Network Enabler's sender interface:
```
Do you want to use selective updates to determine the action to be taken on receipt of a message for an unreachable
                                        domain(y/n)?
```
To configure selective updates on the Network Enabler's sender interface, answer y to the following create_config.info question:
```
Do you want to define any selective-updates on the Network Enabler's sender interface (y/n)?
```
The selective updates can operate only on the MtxTcapMsg MDC type.
For more information, see the discussion about selective updates for fallback processing. For information about selective updates, see the discussion about selective updates in MATRIXX Integration.
If you answered y to the following question, configure selective updates on the Network Enabler's domain lookup interface:
```
Do you want to use selective updates to determine the action to be taken on receipt of a message for which the domain cannot be looked up(y/n)?
```
To configure selective updates on the Network Enabler's domain lookup interface, answer y to the following create_config.info question:
```
Do you want to define any selective-updates on the Network Enabler's domain lookup interface (y/n)?
```
The selective updates can operate only on the MtxTcapMsg MDC type.
For more information, see the discussion about selective updates for fallback processing. For information about selective updates, see the discussion about selective updates in MATRIXX Integration.
Restart the MATRIXX Engine:
restart_engine.py