i rules

how to create i rules for the below

Front-end rules

Match the following URLs, attach them to the front-end IP address, and redirect traffic to the delivery servers:

• ^/delivery/.*
• ^/[a-zA-Z0-9_]*/delivery/.*
• ^/[a-zA-Z0-9_]*/perception/.*
• ^/[a-zA-Z0-9_]*/perception
• ^/[a-zA-Z0-9_]*/open/.*
• ^/[a-zA-Z0-9_]*/open
• ^/[a-zA-Z0-9_]*/session/.*
• ^/[a-zA-Z0-9_]*/session
• ^/[a-zA-Z0-9_]*/observer/.*
• ^/[a-zA-Z0-9_]*/observer
• ^/[a-zA-Z0-9_]*/testcenter/.*
• ^/[a-zA-Z0-9_]*/testcenter
• ^/lobby
• ^/lobby/.*
• ^/rts
• ^/rts/.*
• ^/deliveryodata
• ^/deliveryodata/.*
• ^/LRSEndPoint
• ^/LRSEndPoint/.*

Default traffic should be sent to the shared services servers in large layouts.

In large layouts, affinity or persistence needs to be set to the shared servers. It is suggested to use cookie-based affinity tied to a URL rule for:

• ^/em/.*

Back-end rules

Match the following URLs, attach to the back-end IP address, and redirect traffic to the ETL server:

^/qm.etl.services/.*

​Match the following URLs, attach to the back-end IP address, and redirect traffic to the shared services server:

^/identityprovider/.*