Cisco Tidal Enterprise Scheduler 6.2 Self Service Adapter Guide
- Updated:
- May 23, 2014
Chapter: Deploying the Packages
Deploying the Service Adapter Package
A person with permission to deploy the Service Adapter package must select the received package from the target site and run the deployment. Log files record all activity that occurs within Service Catalog on each site. It is important to save packages each time entities are added or removed, or the package definition is modified.
To deploy service adapter package, perform the following tasks:
a.
Login into Cisco Service Portal as admin and navigate to the
Catalog Deployer
module.
b. Click the
Action
button, then select
Import
from the context menu.
c. Browse to the package, and then click
Import
.
Step 2 Import the Organization, Roles and People. See also, Organizations, Roles and Users Preparation.
a. Click the
Action
button, then select
Import
from the context menu.
b. Browse to the OrgUnitsRolesPeopleCategoriesEmails.xml file in the
C:\TES_CSPwin94_Packages\TESOrgUnitsRoles
folder, and then click
Import
.
c. Deploy the OrgUnitsRolesPeopleCategoriesEmails.xml file.
Importing and Deploying the Agent Packages
A person with permission to deploy the Agent packages must select the received packages from the target site and run the deployment. Log files record all activity that occurs within Service Catalog on each site. It is important to save packages each time entities are added or removed, or the package definition is modified.
To import and deploy the Agent packages:
Step 1 Import the Agents packages from the
TESAgents
folder
a. Click the
Action
button, then select
Import
from the context menu.
b. Browse to the following files located in the
C:\TES_CSPwin94_Packages\TESAgents
folder, and then click
Import
.
Step 2 Deploy each imported xml file.
Step 3 Verify the imported Agents, transformations associated with Agents from the Service Links.
Step 4 Configure the TES Adapter
Outbound
and
Inbound Properties
with the following:
- TESUsername – the username the adapter uses to sign into TES. This user should be properly configured in TES such that the access level and workgroup membership are appropriate for jobs to be exposed via the self-service portal.
- TESPassword – password for the TES user.
-
TESUrl
– the URL for the TES REST API call in the format of
http://tesclientmanager_host:port/api/plugin_name .
For example: jdbc:sqlserver://<DBSERVER>:<DBPORT>;databaseName=RequestCenter
- NSDBPoolMinIdle – the database connection pool minimum idle setting. Default is 1.
- NSDBPoolMaxIdle – the database connection pool maximum idle setting. Default is 3.
- NSDBPoolMaxActive – the database connection pool maximum connection size. Default is 3.
- NSDBPoolMaxWait – the maximum wait time for connection from pool to be available. Default is 10,000 (10 seconds).
- UserDomain – the domain name to be used when users from Cisco Service Portal interacts with TES.
Step 5 Start the Control Agents from the Service Links.
Deploying the Admin Services Package
A person with permission to deploy the Admin Services package must select the received package from the target site and run the deployment. Log files record all activity that occurs within Service Catalog on each site. It is important to save packages each time entities are added or removed, or the package definition is modified.
To deploy the Admin Services package:
Step 1 Import the Admin Services package.
a. Click the
Action
button, then select
Import
from the context menu.
b. Browse to the TESAdminServices.xml file located in the
C:\TES_CSPwin94_Packages\TESAdminServices
folder, and then click
Import
.
Step 2 Deploy the TESAdminServices.xml file.
Step 3 Verify the Admin Services Refresh Standards and TES Standard Migration files from the
MyServices
module.
Importing and Deploying the TES Services Package
An exported package needs to be imported into the target system. A person with permission to deploy the Admin Services package must select the received package from the target site and run the deployment. Log files record all activity that occurs within Service Catalog on each site. It is important to save packages each time entities are added or removed, or the package definition is modified.
To import and deploy the TES Services package:
Step 1 Import the TES Services package.
a. Click the
Action
button, then select
Import
from the context menu.
b. Browse to the TESServices.xml file located in the
C:\TES_CSPwin94_Packages\TESServices
folder, and then click
Import
.
Step 2 Deploy the TESSerivces.xml file.
Step 3 Verify the TES Services (
Launch
,
Rerun
,
Cancel
,
Hold
and
Resume
) from the
Catalog Deployer
module.
Importing Portal Pages and Portlets
An exported page needs to be imported into the target system.
A person with permission to deploy the Admin Services package must select the received package from the target site and run the deployment.
Log files record all activity that occurs within Service Catalog on each site.
It is important to save packages each time entities are added or removed, or the package definition is modified.
To importing the Portal pages and Portlets:
Step 1 Copy and paste the
C:\TES_CSPwin94_Packages\TESCustomFiles\custom\CiscoCloudScheduler
folder to the deployed
C:\jboss-as-7.1.1.Final\standalone\deployments\RequestCenter.war\custom
folder.
Step 2 Import the Portal pages.
a. Login into Cisco Service Portal as admin and navigate to the
Portal Pages
module.
b. Click the
Action
button, then select
Import
from the context menu.
c. Browse to the TESPortalPages.xml file located in the
C:\TES_CSPwin94_Packages\TESPortalPages
folder, and then click
Import
.
d. Verify the imported portal pages in the
Cisco Cloud Enterprise Scheduler
,
My Workspace
and
System
portal pages groups.
a. Login into Cisco Service Portal as admin and navigate to the
Portal Designer
module.
b. Click the
Action
button, then select
Import
from the context menu.
c. Browse to the TESPortlets.xml file located in the
C:\TES_CSPwin94_Packages\TESPortlets
folder, and then click
Import
.
d. Verify the imported portlets in the
HTML
,
JavaScript
and
Services Portlets
groups.
Feedback