Please refer:
Global Configuration of Staging
- Call SAP NetWeaver Administrator.You can use the following address: http://<host>:<port>/nwa
- Choose
![Start of the navigation path]( "Start of the navigation path")
Configuration Management![Next navigation step]( "Next navigation step")
Infrastructure![Next navigation step]( "Next navigation step")
Java System Properties![End of the navigation path]( "End of the navigation path")
. - On the Services tab, select XPI Adapter: XI .
- Enter values for the xiadapter.stage.conf property.
- You can enter 0, 1, or 3 for each processing step ( BI, MS, and so on).
Reference:
Global staging/logging
Message staging and logging behavior is configured adjusting corresponding properties of the J2EE service XPI Adapter: XI:
- Property xiadapter.stage.conf– for staging configuration;
- Property xiadapter.logger.conf– for logging configuration.
For both mentioned properties, value syntax is composed by specifying processing step(s) and staging/logging mode (condition) for each of specified processing step. If messages should be staged/logged at several processing steps, respective step/mode pairs are delimited with comma ( , ).
Possible processing steps and modes that are relevant for staging are provided in tables below:
| Processing Step | Description |
|---|---|
| BI | After sender adapter processing, but before inbound schema validation |
| VI | Before scenario look-up step (check if scenario is local Advanced Adapter Engine based or dual-stack based involving Integration Engine) |
| MS | Before mapping step |
| AM | After mapping step, but before outbound schema validation |
| VO | After outbound schema validation |
| Mode | Description |
|---|---|
| 0 | MODE_NO_STORE: No message persistence (staging) |
| 1 | MODE_STORE_ON_ERROR: Message is persisted only if its next processing step (stage) throws an exception |
| 2 | MODE_STORE_AND_CONTINUE: Message is persisted and processing is continued with the next step. If its next processing step throws an exception, the processor reschedules the message from this storage and returns Note: the mode is deprecated in PI 7.31 due to performance inefficiency during message persistence |
| 3 | MODE_STORE_AND_RETURN: Message is persisted and rescheduled, processing is continued with the next step |
For logging, only processing steps BI, MS and AM are relevant.
Mode values that are relevant for logging are derived from 'basic' 4-bit binary values by summarization of respective 'basic' binary values and its further conversion to a decimal value. Relevant 'basic' values are enumerated in the table below:
| Binary Value | Description |
|---|---|
| 0000 | No logging |
| 0001 | Asynchronous messages are logged |
| 0010 | Synchronous messages are logged |
| 0100 | Onlу еrrοr mеѕѕаgеѕ аrе lοggеd |
| 1000 | Logging with cοntеnt hіdіng (payload is hidden) |
Reference:
Message Staging and Logging Options in Advanced Adapter Engine of PI 7.3x
Regards,
Nabendu.