DSauve
Legendary Poster
I am trying to get multiple foundations set up to test SP18.1, and am at one of the last steps, which is to build the server package.
Some history: I built a full package DV7333FB for client only from the Deployment Server, and then loaded this package on a client. Then I thought I'd build the server package from that client. So I went into Package Revisions, unchecked Client and Checked Server, and submitted off the build.
The problem is that it began by building the specs again. Is there any way around this? It seems like a total waste of time, since I have the specs already built from the client package. Should I do this on the Deployment server (which is where I built the client package) instead? If so, JDE's documentation says to change the JDENET port number in the JDE.INI file on the deployment server. If I do this, can other production users still correctly accept update packages?
Any guidance would be appreciated.
Don Sauve
Wagstaff, Inc.
OW XE, Update 1, SP15.1, HP-UX 11.0, Oracle 8.1.6
Some history: I built a full package DV7333FB for client only from the Deployment Server, and then loaded this package on a client. Then I thought I'd build the server package from that client. So I went into Package Revisions, unchecked Client and Checked Server, and submitted off the build.
The problem is that it began by building the specs again. Is there any way around this? It seems like a total waste of time, since I have the specs already built from the client package. Should I do this on the Deployment server (which is where I built the client package) instead? If so, JDE's documentation says to change the JDENET port number in the JDE.INI file on the deployment server. If I do this, can other production users still correctly accept update packages?
Any guidance would be appreciated.
Don Sauve
Wagstaff, Inc.
OW XE, Update 1, SP15.1, HP-UX 11.0, Oracle 8.1.6