Who is the section for?

This page is dedicated to person responsible for BECS administration. BECS admin supports and maintains BECS integration solution in productive running as well as solves and responds to BECS related problems arising in the production environment. Because admin team has to maintain whole company environment, it is required to keep all project tiers (DEV, QAS, PROD) balanced and adapt any environment update to all of them.

Who am I?

BECS admin is the member of group of standard company administrators. As is clear from standard admin role scope, these professionals are taking care about up and running application servers as well as dedicated productive solutions running on it. BECS admin is required to has the admin knowledge of the BECS environment and detailed knowledge of productive solution architecture and working conditions. BECS admin needs to be able to analyze the problems in BECS integration solution running.

What are required skills I need to have?

The BECS admin needs to have good knowledge of technical architecture on which is running the BECS solution. This professional has to be able to completely reinstall solution if any HW component fails and needs to be able to identify the problem why solution is not working as agreed on signed test cases. For this BECS admin must have the admin knowledge level of BECS (see below).

What needs to be ready before starting my work?

The BECS admin needs to have a tested and implemented integration solution. One of the main requirements is to know the integration solution architecture in detail and has good knowledge of all technical aspects of administered BECS integration solution.

When my role starts in overall BECS integration project?

The admin role arises when the tailor-made integration solution is already implemented, tested and used on QA environment. Standardly is BECS admin in the user IT team who creates the productive environment.

What is my task list?

The administration of BECS involves:

• Assistance on building the BECS solution environment
• BECS Windows Services check
• Event log viewer - system logs, errors and events
• Connection to remote computers
• Check of SQL user validity and user rights
• Check of accessibility of SQL Server objects
• BECS Integration Server health monitoring
• Password and user management – updating in relevant BECS component based of solution architecture
• Connectivity tests
• Checking the solution logs for each BECS solution component
• Notepad usage for viewing log files