About Us

Official OpenText Partner and Enterprise World Sponsor

Founded in 2005

Based in San Francisco

Clients in:

•  Banking

•  Education

•  Public Utility

•  Engineering

•  Legal

•  Government

Team includes the former Vignette Portal Engineering Team Lead and the

Program Director of the Vignette Portal/Builder.

Why Siterise?

•  Eases complexity of OpenText’s Customer Experience Platform (CEM)

•  Unifies Development, Staging, and Production

•  Reduces risks with pushing updates to Production

•  Speeds development and minimizes painful clicks

•  Reduces downtime with targeted deployments

Simple one-click install on Windows/Linux/Mac

Key Features

•  Inline editor to make JSP/CSS/XML/XSL changes

•  Integrated Source Control to prevent loss

•  Compare environments to see differences

•  Create custom deployment packages for targeted updates

•  Drag-and-drop assets from a filesystem or desktop

What difference can it make?

•  Increase Developer / Administrator productivity •  Roll out site releases faster •  Incorporate Source Control to track changes and

roll back •  Diminish risk and downtime by promoting only the

required components – eliminate/reduce full site export/import procedures

•  Increase site reliability by comparing and syncing environments

•  Get backend system metrics

Connect Multiple Stages

Single umbrella over Development, Staging and Production

Connect Multiple Products

WEM

Content Server

Media Manager

Tempo Social

With Siterise you can: •  Change Portlets •  Edit Display Templates •  Create Targeted Deployments •  Manage Complex Configurations

OpenText Portal

Works across the OpenText Customer Experience Management (CEM) Suite

Features

Rapid Editing

Problem: “I need to quickly change a JSP/XML/XSL file page.”

Before: Lots of clicking around looking for right file and then either manually repackage or do a full site export import.

With Siterise: Search for the file, make changes, and either push out individual files or use the drag-and-drop CAR repackaging tool.

Rapid Editing 1:#Search#for#File#

2:#Make#Changes#

3:#View#Directly,#Deploy,#

or#Repackage#

Selective Deployment

Problem: “I have some site changes, but I want to minimize downtime and risk.”

Before: Full site export and import. Lots of downtime and lots of crossed fingers.

With Siterise: Select multiple components, right-click or drag the components to repackage them.

1:#Select#one#or#more#desired#components#

Selective Deployment

3:#Custom#bundle#can#be#checked#into#source#control#and#deployed#

2:#Repackage#selected#components#into#a#custom#bundle#

Compare Deployments

Problem: “I’m not sure of all of the components that have been deployed to production. I need a way to compare what is on my Development, Staging, and Production environments.”

Before: Lots of tedious error-prone work.

With Siterise: Select the environments to compare, look at the specific differences and optionally reconcile those differences.

Compare Deployments (1/3)

1:#Choose#targets#for#comparison#

Compare Deployments (2/3)

2:#See#comparison#results#

Compare Deployments (3/3)

1:#See#differences#2:#Click#to#sync#

File History

Problem: “I need a way to see which changes were made to a particular file.”

Before: Create a custom development process and ask that developers check in their work into a source control system regularly. A mistake uploading could lead to code loss.

With Siterise: Team members can look at the changes and potentially revert back to an earlier version. Using

File History

1:#Select#version#and#see#which#developer#made#the#change#

2:#Click#to#sync#changes#

Quick Transfer

Problem: “I’ve developed some components on my development environment and I want to selectively choose some of them to be deployed to a staging environment so other team members can review.”

Before: Lots of clicks to find components, more clicks to transfer them to the file system, and more clicks to upload them to the new destination.

With Siterise: Right-click or drag-and-drop the components into the Staging environment.

Quick Transfer

1:#DragEDrop#Component#into:#E  Another#environment#E  Scratchpad#E  Desktop#E  Source#Control#Directory#

Edit WEM/Tempo Social Templates

Problem: “I need to make some changes to the templates to reformat the way that my content is displayed.”

Before: Connect to the machine where the exploded WAR file resides, make changes, and repackage the war file for deployment.

With Siterise: Edit the template directly and optionally right-click to deploy the file to another environment.

Edit WEM/Tempo Social Templates

Configuration Management

Problem: “There are some very subtle configuration problems that are causing intermittent and difficult to trace issues.”

Before: Review each of the nodes in a cluster with a fine tooth comb.

With Siterise: Immediately see the differences of different files or database values as they may exist.

Configuration Management

1:#Compare#individual#nodes#

3:#Merge#and#make#changes#immediately#in#the#twin#pane#

2:#SeGngs#may#be#either#based#on#property#files#or#database#values.#

Single Console

Problem: “All of the different CEM consoles are confusing. I would like to have a single location where I can get access to the entire platform.”

Before: Multiple consoles, multiple panels, challenging interfaces, and lots of clicks.

With Siterise: Select from over 15 different reports to look at. Reports are AJAX safe and include cluster performance information.

Single Console

Manage#OpenText#Products#

Manage#Underlying##Web#ApplicaPon#Server#

Troubleshooting - Links and UIDs

Problem: “I’m having trouble with the platform and I need to track down the source.”

Before: Hunting and guessing where the problem may lie.

With Siterise: Quickly identify where the problems are and get quick access to the appropriate OpenText Console.

Troubleshooting - Links and UIDs

Universal#IdenPfiers#are#exposed#

Quick#link#to#jump#to#the#right#place#in#the#OpenText#

Console#

Troubleshooting - Logging

Problem: “Going through all of the different console to try to find a problem is tedious.”

Before: Tailing files and/or logging into multiple clunky web interfaces.

With Siterise: Use tabs to navigate across multiple log files. Errors jump out in red and the searchable log file can easily have a new log level set.

Troubleshooting - Logging

MulPple#log#files#in#tabs#

Errors#jump#out#in#red#

Search,#Clear,#Set#New#Log#Level#

Troubleshooting - Getting Help

Problem: “We’re having trouble and we need to resolve an issue quickly.”

Before: Lots of back and forth with support teams.

With Siterise: Issue reporting is built into the product. With a couple of clicks, you can report an issue to us and the relevant log files and screenshots will be forwarded to us. We can help identify and quickly resolve issues. We can also help formulate a problem statement to open an OpenText Support Ticket.

Troubleshooting - Getting Help

AWach#relevant#files#without#a#lot#of#back#and#forth#

One#click#to#start#process#

Server Analytics

Problem: “I need to get some technical information about the platform.”

Before: Use a third-party tool that sends information outside the firewall and does not provide pertinent backend data.

With Siterise: Select from over 15 different reports to look at. Reports are AJAX safe and include cluster performance information.

Server Analytics 1:#Select#1#of#15#reports#

2:#Print#or#Export#Chart#or#CSV#Report#

3:#Filter#with#Criteria#

Why Sutro Software?

Focus – Sutro is the only company solely focused on improving the daily lives of OpenText administrators and developers.

Agility – Sutro’s development process is highly agile, iterative, and customer-focused. Most issues are fixed the day they are reported, and most enhancement requests make it into the product within a week or two.

Access – Sutro customers don't encounter layers of support and Byzantine processes – they have direct access to the Sutro engineering team, and are considered valuable product development partners.

Experience – Sutro Software products are backed by full training, support, and consulting services. Sutro's broad industry experience and deep insider knowledge will help make your project a success.

Frequently Asked Questions (1/2)

What are the desktop requirements? –  Windows/Linux/Mac

What are the system requirements? –  Siterise is compatible with Portal 7.1 and above. We are OpenText

partners and because we get early releases we are able to ensure compatibility as new releases come out.

Do I have to install anything on the server? –  No. Siterise will seamlessly deploy an Admin Component onto the

platform screen.

How do I uninstall Siterise? –  Simply remove the program from your desktop machine and click on

the Remove Adapter button.

Frequently Asked Questions (2/2)

Is Siterise cluster safe? –  Yes. Siterise uses the Deployment API to load components.

What credentials do I need? –  You need Server Admin privileges on the deployment that you wish

to connect to via Siterise. In the 5.0 release we will be introducing a Read-Only mode.

Is Siterise compatible with SSO systems and custom authenticators?

–  Yes and we will help you set up the Siterise configuration.

Download Evaluation From:

http://www.sutrosoftware.com/