Browse Prior Art Database

Method to Automate and Personalize/Configure a System for deploying the System into a Specific Landscape/Software-As-A-Service (Saas) Solution Instance

IP.com Disclosure Number: IPCOM000198383D
Publication Date: 2010-Aug-06
Document File: 4 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method is disclosed to automate and personalize/configure a system such that the system can be deployed into a specific landscape and/or Software-as-a-Service (SaaS) solution instance.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 1 of 4

Method to Automate and Personalize /Configure a System for deploying the System into a Specific Landscape/Software-As-A-Service (Saas) Solution Instance

Disclosed is a method to automate and personalize/configure a system such that the system can be deployed into a specific landscape and/or Software-as-a-Service (SaaS) solution instance.

Consider a z/OS system for illustration purpose. In order to allocate, configure and deploy a z/OS system into a service landscape, the method starts by allocating a virtual server with a specified set of resources such as CPU, memory and DASD (e.g., minidisks). Thereafter, the method deploys/installs a z/OS system (image) into the virtual server. This includes flashcopy (such as dedicated disks) of necessary user disks, and / or link to a set of shared system disks (OS itself). Subsequently, connectivity for initial access to the system is configured. This includes configuring network links, IP addresses, host name, domain name etc. This can be done via writing TCP/IP configuration using z/OS symbolics to a shared boot disk to which the z/OS system is to be linked (read access).

Finally, the system is booted up and the personalization/configuration process is continued by automatically logging in to the system (e.g., via FTP - File Transfer Protocol) and executing a set of JCL jobs (JCL - Job Control Language; also can be Rexx, or other scripting language) specifically specified for the z/OS image.

When a z/OS system is booted, a set of jobs (JCLs, scripts) are run to configure/personalize the system before it is ready to provide services. The personalization/configuration process includes, but not limited to:

Configuration of TCP/IP network for connectivity including addition IP addresses, capability
Configuration of user access information (RACF - Resource Access Control Facility)

Configuration of network firewall to limit access and protect system from attacks
Configuration of IP Security to protect traffic sent/received to/from other systems within and outside of the specific landscape to which the system belongs
Configure/Activate Intrusion Defense Services
Subsystem/Software (e.g., DB2, CICS) initialization

The method introduces a framework for specifying the JCLs (or scripts) to be run in an order that they're required to follow, and parameters that need to be tailored to the system that is being provisioned to support the specific landscape.

The framework includes a specification of the set of JCLs that need to be run for specific subsystem along with the symbols to be replaced within each JCL and what is expected as the result of each JCL ( Configuration File ). A sample configuration file is

1

Page 2 of 4

shown below:

DPTC39.SOARAMP.LOADPARM(IEASYMDB

)<

/SymbolicsFile>

DPTC39.SOARAMP.LOADPARM(IEASYMR1

)<

/SystemSymb

olicsFile>

HFS<

/Name>

DPTC39.SOARAMP.JOBLIB<

/JobLocation>


DPTC39.SOARAMP.LOADPARM(IEASYMDB

)

<

/SoftwareSymbolicsFile>

HFSREST<

/Name>

HFSREST<

/JCLName>

0000<

/ReturnCode>

&...