|
Home
| |
" The operations support area needs
to be well skilled in order to handle the support requirements when going live. The
initial period during go live may be intense, requiring twice or three times the amount of
normal support. This intense support requirement will dwindle a couple of months after go
live..."
Various areas, pertaining to the Operations / Production environment need to be
addressed BEFORE you go live:
ALE Administrator role
defined and sourced. Responsible for ALE configuration and issue resolution.
Capacity plan including
ALE IDoc archiving strategy - Consider the growth of the ALE
solution, procedures the archiving of IDocs while considering the legal implications.
ALE Operations role
defined and sourced. Responsible for ALE archiving, background job scheduling and
monitoring.
ALE failure recovery
procedure - When a soft failure occurs (I.E. When a system is restored to a previous
point in time) a recovery procedure needs to be implemented... How?
Define the ALE support
organization structure. The ALE administrator will receive the ALE problems
when in production. Using a troubleshooting guide the problems can be resolved.
Other considerations
 | Never do client copies... If you do, check on:
 | the change pointer table (BDCP/S); |
| the IDoc table (EDIDC/S); and |
| all the logical system references. |
|
| Client specific configuration:
| Immediate processing on the outbound and inbound side should be avoided due to the fact
that ALE takes every available dialog process, on the receiving system, when performing
the send. |
| Configuration needs to happen, on-line, in production systems for
versions up to V4
|
|
| Error handling: Workflow is used to trap error messages. If you have MS
Exchange then consider implementing the integration between MS and SAP as this will help
the ALE administrator with 1 in-box of errors as apposed to 1 per client that he supports
|
| ALE specific scenarios
| The classification master and it's respective master data object (vendor, material or
customer) are not linked, in any way, via ALE message types up to V4. This implies that
the classification master may end up on systems where it is irrelevant. |
| OSS notes need to be implemented to improve the speed of the programs
RBDAPP01, RBDMANIN, RBDMIDOC, RBDSTATE.
|
| OSS note needs to be implemented to get the ALE recovery tool. BDRC and
BDRL.
|
|
Deliverables before / during this stage
| ALE Administrator Troubleshooting Procedure - What to do when the
unexpected happens... |
| ALE Archiving strategy and procedure - When and how are you going to
archive the IDocs. Remember the legal implications. |
| ALE Capacity Planning Guide - Check the growth and plan for expansion. |
| ALE Failure and recovery procedure - In case a system needs to be
restored to a point back in time, how do you recover??? |
| ALE Background Job Scheduling Procedure - Example of how to
configure ALE for use with background jobs as opposed to immediate processing . |
| ALE Performance Testing & Tuning Guide - Some tests done to measure
performance, together with the results and recommendations. |
| ALE Production client cleanup procedure - When a client is created,
what steps do you need to take to clean it up? When a system is brought down what do you
need to check? |
|
