Server Packages

Being new to CNC, just a quick question. what is the rule of thumb for when
to deploy a package to the enterprise server and when to just deploy client
packages? Do you always build a package for both? Sorry, I am confused.
Thanx.

AS400 V4R5 XE 17.1 U3 NT W2K

Libbi Fletcher
Systems Administrator
HoMedics, Inc.
3000 Pontiac Trail
Commerce Township, MI 48390
248-863-3001 ext. 1281

“The rule of thumb for when to deploy a package to the enterprise server?”

Make sure none of the OneWorld UBE is running in the subsystem in the same environment.

“When to just deploy client packages?”

Make sure none of OneWorld user is using OneWorld on that terminal server.

“Do you always build a package for both?”

Don’t be sorry. I was once like you, confused, 3 years ago. You do not have to always build client and server package. It depends on your objects/application. For example, if P554210 was developed and needs to be built and deployed, all you need is to build an update client package. Because APPL is a client application runs on the PC. If R5542750 was developed and needed to be built and deployed, you would need to build and deploy an client and server update package because UBE/ERW can run both on the server and fat client (not zero client) but it always submitted on the client side first before running on the enterprise server.

Here are the examples:

Client package: APPL (example P4210, P4310 and etc.), BSFN and Data Structure Templates, UBE, Table and BSVW.

Server package: Every object above except for APPL.

BSFN can be client and/or server depending on the programmer who developed it.

Make it easy on yourself- build combined (Server+Client) packages and deploy to the Enterprise Server when you depoy the package.

Hi Libbi,

Take a look to "Package Build Under the Covers" powerpoint presentation. There is a lot of information on it.

You can find it on KG searching for "Package and build and covers".