brought to you by

BIZTALK SUMMIT 2014, LONDON

MARCH 03-04sessions. discussions. networking and

more

What if you mess it up?Tord Glad

Nordahl

• BizTalk Administrator Expert• Microsoft Integration MVP• Training• Health Checking• Debugger• Speaker• Active contributor at TechNet• Active blogger• In general a Glad guyn.com

2

Profile

Profile

Tord Glad Nordahl

So you need to know this• Configuration• Cleaning• Limiting• Expanding• Following best practice• When to not follow best practice

How do Admins mess it up?

Backup job

We have our own way of doing it

We have a snapshot

of the server

We don’t need a backup

Configured but files

are deleted instantly

It failed so much that

we disabled it

It backs up the databaseAnd clean the junk in the

trunk!

DTA cleanup

We dont want to,

we archive everything

here

we don’t need the

data

We don’t know how

to configure

it

Is this job even

important?

It failed so much that

we disabled it

It cleans the tracking database

and stores the archive for it

SQL Agent

Oh, did we forget to start it?

It uses too much

resources

It keeps failing, so we stoped

it

None of the jobs

were working anyways

We have a schedule job for that

All cleanup is done by SQL JobsIf this isnt running, nither will

BizTalk

Host security

Super admins

runs it all, at least it

works

Oh, we can’t use

local users?

That will be a lot of

work

We have a strong

password for it

It’s easier when we update

passwords

Don’t mix procesess and users

Keep security high

Host Seperation

We have 100 hosts, so we are

good

The default

host always work

We don’t need one for each

task

They are seperated

on different

machines, see?

Tracking host?

They all do

tracking

Seperate hosts based on purpose

Keep it easier to administrate

Artifact tracking

We need debugging informatio

n

This is our backup?

Oh, do we have

tracking data?

We have it on for some

applications

We use it to improve performanc

e

Artifact tracking may impact performance

Limit what you track

Throttling

We turned of

throttling!

Yes, we just

expand with more hardware

No, our setup is running perfect

I don’t think we

have accelerato

rs here.

Yes, i see someone using it.

Thorttling will prevent complete stops

Throttling can limit throughput

Databases

So 100gb is too much?

Will a big spool table

impact BizTalk?

We have plenty of

free space, but BizTalk is

slow

They are seperated

on different

machines, see?

DebugTraceyeah we have a big

one!

Large databases impact performance

Monitor the databases

Monitoring

Oh, we don’t have

admins

Nothing fails here.

Is there tools for

that?

Yeah, we log on to

the server everyday

Yeah, we monitor it at least once a month

Monitoring is just not the hubYou need to monitor every aspect of

BizTalk

Unused programs and services

Yeah, we print from

BizTalk Servers

We need to develop

straight into

production

We need office so

we can use outlook from the server

We don’t need the

entire sharepoint installatio

n?

I love to have

installation files

available

The server is ment to run BizTalkOther artifacts may interfear with

performance

Hardware

So 10gb windows drive is small?

We wanted 120gb og

RAM because of a memory

leak

We are just used to always have this

We scale by

ordering a new

machine

As long as it works it’s good enough

Hardware is important…But don’t go crazy or be a cheap

ass

Over to developer mess, we all have it

Event logs

Let’s spam the event

log!

Processing a message

is an event

Who uses the event

log?

Yes, we use them

for logging… EVERYTHIN

G

We write general errors here

Keepin’ it clean!Unless you need the data in the log, keep it

clean

Lets make an

adapter!

How did i do it again? Lets make

it in C#

Coding…

Let’s use a lot of

persistencepoint for no reason

Spamming the group

hub is awesome!

Screw good error messages!

…continue!

Nobody will ever read my

code anyways

Admins don’t need

any test messages

Oh yeah, I did test

it…

Lets put this in the same app as usual

Lets use the BizTalk

Config file!

Bad development impact • Performance• Administration• Support• Scalability• Durability• and so om

Orchestration

We don’t use

orchestrations

just pipelines

All message shall go through one orch

Let’s debatch in

the orchestraio

n

We don’t use

pipelines, only

orchs!

Persistencepoints,

more more

more!!!

Use orchestration the way it’s meant

Don’t let the orchestrations be the bottleneck

?QUESTIONS