Everyone loves a good tip, like using toothpaste to clear up hazy car headlights. In this session, Identity users will learn from the master, our lead architect, Lisa Lombardo, as she goes through tips and tricks to make sure you’re getting the most out of your IAM deployment. Come with your questions about Core Access, Core Compliance, and Core Password.

1. ACCESS
ASSURANCE
SUITE
TIPS
&
TRICKS
Lisa
Lombardo,
Principal
Architect
of
Identity
Product
and
Technology
Solutions

2. L E A R N M O R E
Lisa
Lombardo
Lisa
Lombardo,
Principal
Architect
of
Identity
Product
and
Technology
Solutions

3. AGENDA
-­‐ Tips
&
Tricks
• For
Maintenance
• For
Functionality
• For
the
Administration
Manager

4. M A I N T E N A N C E

5. Maintenance
• Windows
services
startup
• Windows
updates
• Log
archiving
• Database
maintenance

6. Maintenance
– Windows
Services
Subtitle
left
• There
is
a
proper
order
to
start
the
Windows
Services
of
the
Access
Assurance
Suite
• Knowledge
article
provides
a
PowerShell
script
to
stop
and
start
the
services
in
the
proper
order
• Especially,
the
CourCFService before
the
CourCFMService before
the
CourionService
• The
CourProfiler service
should
start
first,
as
it
is
responsible
for
logging
done
by
all
other
components.
• The
CourConfigSvr service
should
start
second,
as
it
is
responsible
for
reading/writing
of
configuration
data
used
on
initialization

7. Example
Subtitle
left
#
Now
all
the
services
will
be
started
in
a
logical
order.
#
Please
put
a
"#"
in
the
first
column
of
any
entry
below
for
services
your
deployment
does
not
use
funcStartAndWaitCourProfiler 1
FuncStartAndWaitCourConfigSvr 1
funcStartAndWaitCourCFService1
#
Increase
this
wait
time
if
you
have
a
large
number
of
targets
funcStartAndWaitCourCFMService10
#
Increase
this
wait
time
if
you
have
a
large
number
of
targets
funcStartAndWaitCourionPasswordCourier 10
funcStartAndWaitCourProtocolService1
funcStartAndWaitCourGATService1
#
if
using
Transparent
Synchronization
funcStartAndWaitCourionTSAO1
#
if
using
Transparent
Synchronization
funcStartAndWaitCourNSLDAPAgent1
#
if
using
PMM
for
Netscape
DS
funcStartAndWaitCourATLService1
funcStartAndWaitCourATLAdmin 1
funcStartAndWait"Courion Session
Claim
Provider"
1
funcStartAndWait"Courion Community
Claim
Provider"
1
funcStartAndWait"Courion Eventing Service"
1
funcStartAndWait"Courion Macro
Engine"
1
funcStartAndWait"Courion Identity
Mapping
Service"
1
funcStartAndWait"Courion Notification
Service"
1
funcStartAndWait"Courion Request
Service"
1
funcStartAndWait"Courion Scheduler
Service"
1

8. Maintenance
– Windows
Updates
Proclaiming
from
the
mountain
top!!!
“Stop
all
Access
Assurance
Suite
Windows
services
before
applying
Windows
updates!”

9. Maintenance
– Windows
Updates
• You
do
not
change
your
oil
on
your
car
while
driving
down
the
highway.
• Please
do
not
change
the
underlying
operating
system
with
the
Access
Assurance
Suite
component
running.
• WMI
(Windows
Management
Instrumentation)
layer
corruption
has
occurred.
• WMI
holds
some
of
our
configuration
data.
• Uninstall
and
re-­‐install
is
needed.
• Use
ConfigMover Targets
and
ConfigMover Workflows
to
export
targets
and
workflows
for
import,
if
needed.

10. Maintenance
– Windows
Updates
• While
you
are
stopping
the
Access
Assurance
Suite
services,
regularly
archive
your
log
files
to
keep
them
of
a
manageable
size
• If
you
do
not
have
your
own
methodology
for
archiving
logs
of
your
enterprise
applications,
the
PowerShell
script
provides
an
option
to
archive
the
logs
• CourProfiler service
controls
the
logs.
• Must
be
stopped
to
release
the
file
for
move
to
another
location
• New
logs
automatically
re-­‐create

11. Maintenance
– Log
Archiving
• Over
time
the
logs
can
get
large
and
eventually
unopenable by
common
editors.
• When
working
a
support
case
the
logs
are
vital
to
the
investigation.
• Regularly
archiving
the
log
files
when
doing
other
maintenance
tasks
on
the
application
server
is
recommended.
• The
Knowledge
article
with
information
on
stopping
and
starting
services
includes
a
PowerShell
script
with
log
archiving
as
an
option
while
the
services
are
stopped

12. Maintenance
– DB
Maintenance
• Over
time
the
database
can
get
fragmented
and
reduce
performance.
• Following
Microsoft’s
recommended
maintenance
plans
for
the
databases
on
database
server
is
recommended.
• We
have
found
large
database
queries
significantly
improve
by
regularly
running
the
DB
server’s
sp_updatestats stored
proc
on
the
application’s
database.

13. F U N C T I O N A L I T Y

14. Functionality
• Performance
• Logs
• Recommendations

15. Functionality
-­‐ Performance
• How
well
is
something
functioning
or
performing
and
from
who’s
perspective?
• Quality
vs
Quantity
(time)
• Tools
for
measuring
performance
and
to
find
bottlenecks
• Fiddler
or
web-­‐browser-­‐based
tools
like
IE
Developer
Tools
• Wireshark
or
network
capture
tool
• Process
Monitor
/
Process
Explorer
and
task
manager
• SQL
Profiler
• Log
files
include
logs
from
the
suite,
IIS
logs,
Windows
logs

16. Data
Flow
XMLAO
IIS
CourATLService
Connection
strings
Courion
Service
CFM CF
DB
AD
RACF
SAP
End
User
Workflow
Browser Other
Courion
Windows
Services
AA
Portal
apps
MSMQhttp…courion...
http…CourionARMS...
Presentation
Application
Cnctr/PMM
CF
AD2
Targets
Initiation
Event
Viewer IIS
Logs
CourionService/
CourATL.log
CourionARMS/*
Portal*.log
CourionService/
*.logs
CourionService/
*cnctr.logs target
artifacts

17. Request
ßàResponse
• Most
activity
is
request/response
based
• Component
sends
request
• Another
component
receives
request
and
acts
on
request
• Sends
response
to
the
component
that
made
request
• Follow
the
“request
to”
and
“response
back”
path
• Can
get
complicated
• The
component
that
receives
a
request
may
have
to
issue
their
own
request
to
another
component
and
wait
for
that
response
before
responding
to
the
original
request
• Network
protocols,
firewalls,
timeouts,
etc are
all
involved
• Determine
what
audit
trail/logs
exist
to
track
the
activity
at
each
component
• Network
capture
tools
to
track
the
activity
between
components
• SQL
Profiler
to
track
the
activity
to
the
database

18. Functionality
-­‐ Logs
• Logging
approach
• All
the
services
have
a
log
file
• CourionService =
courion.log
• Courion Request
Service
=
courrequestservice.log
• All
the
connectors
have
a
log
file
(*cnctr.log)
• Connector
for
Microsoft
Active
Directory
=
adscnctr.log
• Connector
for
Microsoft
ADO
=
adocnctr.log
• All
the
PMMs
have
a
log
file
(*module.log)
• PMM
for
Microsoft
Active
Directory
=
adsmodule.log
• PMM
for
Sun
Solaris
=
unixmodule.log
• Changes
made
in
Administration
Manager
• Audit.log

19. Functionality
-­‐
Recommendation
• Connector
for
Courion
HTML
Email2
• Not
Connector
for
Microsoft
CDO
Message
• Check
courion.log
• Ticketing
• Notifications
• Triggers
• Export
workflows
and
targets
• Document
and
securely
store
pass
phrase

20. A D M I N I S T R A T I O N
M A N A G E R
T I P S

21. Administration
Manager
Tips
• Provisioning
Platform
• Copy
and
Paste
• Workflow
auto-­‐load
• Workflow
selection
• Macro
caching
values

22. Admin
Manager
Tips
– Copy
&
Paste
• Administration
Manager
for
Provisioning
Platform
workflows
• CP=yes
• Enables
Copy
and
paste
of
configuration
from
one
workflow
to
another
• Tree
view
only
• http://localhost/courion/CustMgrs/AccountCourier/Default.asp?cp=yes
• Note:
AAS
9.0
replace
“courion”
with
“core

23. Example

24. Admin
Manager
Tips
– Workflow
auto-­‐load
• Administration
Manager
for
Provisioning
Platform
workflows
• Workflow=<WorkflowName>
• Load
a
specific
workflow.
Workflow
name
is
case-­‐sensitive.
• http://localhost/courion/CustMgrs/AccountCourier/Default.asp?Workflow=<workflowNam
e>
• Note:
AAS
9.0
replace
“courion”
with
“core”

25. Example
http://localhost/Core/CustMgrs/AccountCourier/Default.asp?Workflow=A
PITest
http://localhost/Core/CustMgrs/AccountCourier/Default.asp

26. Admin
Manager
Tips
– Workflow
Selection
• Administration
Manager
for
Provisioning
Platform
workflows
• MW=yes
• On
Administration
Manager
logon
page
presents
list
of
available
workflows
for
selecting
one
workflow
to
load
for
quicker
initialization
of
the
Admin
Manager
• http://localhost/courion/CustMgrs/AccountCourier/Default.asp?mw=yes
• Note:
AAS
9.0
replace
“courion”
with
“core”

27. Example
Subtitle
center

28. Admin
Manager
– Macro
Cache
• Provisioning
Platform
workflow
execution
• Macro
resolution
• Custom
Macro
definition
• Cache
results
– use
for
data
that
does
not
change
during
that
workflow
execution
• Use
optimization
– group
database
queries
that
share
the
same
criterion
from
the
same
table
“
FROM
<table>
WHERE
<criterion>”

29. THANK
YOU