In this webinar, we walk you through the setup and pre-requisites for an easy roll out of Baya V3 with ConnectXF. Learn More: https://blog.mithi.com/webinar-baya-v3-connectxf/

1. Webinar
Rolling out Baya V3 with
Speaker
Anita Joshi
Deployment Manager
Customer Sucess
23 Jan 2019
3:00 PM to 3:30 PM IST

2. Setup

3. A. Network : End User --> Baya 3 (Internet )
Responsibility: Customer
• Network : 1 Mbps per 100 users
• Ports : 443, 8080
Setup

4. B. Baya V3: instance setup
Responsibility: Customer
Setup
• OS : Ubuntu 16.04
• Network
• IP
• Routes
• Gateway
• DNS

5. C. Baya V3: instance setup
Responsibility: Mithi
Setup
• Network
• Hostname
• Firewall
• Docker Service
• Installation
• Configuration
• Install dockers for baya3
• Configure dockers for baya3
• Enable/disable features of baya 3
• Configure address book
• Configure calendar
• Outlook skin license update
• SSL certification configuration

6. C. Network : Baya 3 -> Mailserver
Responsibility: Customer
Setup
• Network : 1 Gbps/10 Gbps
• Ports : 25, 143, 389, 80, 8080

7. D. Network : End User --> Baya 3 (LAN/WAN)
Responsibility: Customer
Setup
• Network : 100 Mbps
• Ports : 443, 8080

8. E. Internal DNS configurations
Responsibility: Customer
Setup
• DNS : Domain name for mail server
mapped to the mail server's internal
ip
• DNS : Domain name for baya 3
server mapped to the baya 3
server's internal ip

9. F. Mail server configuration
Responsibility: Customer & Mithi
Setup
• SMTP Controls : Allow mail traffic
from Baya 3 mail server using smtp
auth
• Baya auth : Allow web service
requests from Baya 3
• Directory : Allow access to LDAP for
Baya 3 internal ip
• Connect XF: update to version 3.28
and patches

10. G. Network : Mail Server -> Baya 3
Responsibility: Customer
Setup
• Network : 1 Gbps/10 Gbps
• Ports : 25

11. H. External DNS
configuration/ Calendar service
event domain name
Responsibility: Customer
Setup
• DNS
• Add a DNS evt.<domainname>
• Add MX for evt.<domainname>
• Mail routing
• Route mail for evt.<domainname>
to the Baya 3 server

12. I. Network : Baya 3 --> Active Directory
Access (Optional)
Responsibility: Customer
Setup
• Network : 1 Gbps/10 Gbps
• Ports : 389 / 636

13. A - Prerequisites
B - Pre Go Live
C - Go Live
D - Post Go Live
PHASES OF
DEPLOYMENTS

14. A: Perquisites
A. Mail Server XF version
Responsibility: Customer/ Mithi
• Connect XF version: 3.28 with latest patches

15. A: Perquisites
B. Baya 3 Server: Hardware and OS configure
Responsibility: Customer
• Server type : Enterprise Grade
• CPU : Minimum 2 core + 1 per 500 users
• RAM : Minimum 8GB + 1 per 500 users
• Network : 1 Gbps/10 Gbps
• Root disk : RAID 10 - 20 GB
• Docker volume : RAID 10 - 200 GB + 10 GB per
500 users
• OS : Ubuntu 16.04 (prefered), RHEL 7

16. A: Perquisites
C. Network components
Responsibility: Customer
• Firewall: Refer to the network details and ports to be opened
mentioned in the setup phase
• WAF: Refer to the network details and ports to be opened mentioned
in the setup phase
• Internet access for Baya 3 instance: Refer to details in setup phase

17. B: Pre Go live
A. Trial
Responsibility: Customer
• Make Baya V3 with a small set of users
This will allow you to check the flow of traffic
between the mail server and Baya V3 and also
iron out any other integration issues

18. B: Pre Go live
B. Admin training
Responsibility: Mithi
• New system: Training on the new architecture
• SOPs: Training on the Standard operating procedures
• Baya 3 features awareness: Will cover key differences between Baya V3 and V2
• SOPs: Training on the Standard Backing up the system Will cover the steps to take regular backups

19. B: Pre Go live
C. Informing the End user
Responsibility: Customer
• What's new and how to use
• Mail to end users with links to training videos

20. C: Go live
Redirect web client traffic to Baya 3
Responsibility: Customer
• DNS change: Updates to the internal and external DNS to access Baya V3
• Load balancer reconfig: In case of a load balanced mail server setup, the
configurations will have to be done on the ELB to allow access from the
Baya V3 server

21. D: Post Go live
A. Monitoring
Responsibility: Customer
• Service monitoring: Resource utilization
• Uptime: System uptime will be the responsibility of the customer

22. D: Post Go live
B. Back up
Responsibility: Customer
• Daily or periodic backup: Customer has to ensure daily backup

23. D: Post Go live
C. Upgrades
Responsibility: Mithi/Customer
• Regular updates and upgrades will be provided as part of the subscription

24. Contact - support@mithi.com