Deploying the BSSV package to BSSV server

Create a valid EnterpriseOne user in Server Manager

Before creating a new E1 Business Services Server we must make sure there is a user created
within Server Manager that will be later deploying the Business Services to the E1 Business
Services Server after setup is complete. This same user must have the permissions to deploy and
configure web products. (Note: When executing the Welcome wizard for Server Manager, you
may import users from an E1 database if you wish.)

1 1. Navigate to the Server Manager Users link

3 2. Scroll to the User Groups section

5 3. Select the button to Create a user group

6
1 4. Create a new group named Web_Admins.

3 5. Select the newly created group.

5 6. Scroll down to the group permissions for the default server group. Grant the
permissions viewGroupMembers and webProductInstance to the Web_Admins user
group.
6

7 7. Navigate back to the management users page. Scroll down to the Management
Console Users section on the page. Select the checkbox next to the JDE user and click
Grant or Revoke User Groups

1 8. Select the Web_Admins group in the popup dialog and click Grant User Group

3 9. This user is now ready to create the instance of EnterpriseOne Business Services
Server and deploy to that instance in the BSSV.
In order to deploy BSSV need to do this from a client which has H4A installed. This is
because it uses the JAS communication with jdbc connections which are already setup
with a webdev client install.

On the Client machine:

E81\DV812\ini\sbf must contain the following files:

jdbj.ini
jdeinterop.ini
jdelog.properties
LocalLogicCatalog.xml
tnsnames.ora

These files should already exist from installing H4A (webDev client)

The jdeinterop.ini file found under this directory must contain Security Server defined

Since the deployment of BSSV from package deployment (P9631) is using JAS
comunication, you need to look at the JAS and Jasdebug logs to find out what is
happening during the process. The jde logs will not give you enough information to
determine what the issue is.

jdelog.properties found under \system\classes controls the JAS logging for deploying
BSSV. Make sure to redirect the logs to an absolute path, otherwise they end up in root
of DV812.

Deploy

1. In order to deploy BSSV need to do this from a client which has H4A installed.
This is because it uses the JAS communication with jdbc connections which are
already setup with a webdev client install.

2. Make sure the EnterpriseOne Services are up and running.

3. Start the JDEdwards Solution Explorer from the desktop.

4. Sign on to the DV812 environment with the JDE user ID.

5. Launch the Package Deployment (P9631) application from the Package and Deployment
Tools (fastpath GH9083)

6. In Work with Package Deployment, click the Add button.

7. Click the Next button to start the Package Deployment Director

8. Select the package that was just built (BSSV_DV) and click Next
 9. Select the Business Service Server and click Next

10. Enter the URL to the ServerManager Management Console and click Next

When entering the URL for Server manager do NOT include the Home part of
the URL. It should look like this:

http://dencmassive.mlab.jdedwards.com:8999/manage

11. Select the EnterpriseOne Business Services Server (BSSV_Server) to deploy the BSSVs
and click Next

12. On the final revisions screen, click End.

13. Expand the package tree that you worked with all the way down to the Business Services
Server. Select the latest date/timestamp and Click on the deploy button.
 14. Select to have the Report Output go to On Screen and click the OK button. That will start
the Package Build UBE (R98825F), which could take as long as 5 minutes to complete.
The BSSVs are deployed to the selected Business Services Servers.

Troubleshooting

BSSV Deploy
1 1. EnterpriseOne User not a ServerManager authorized user

1 a. This happens when you click Next after you specify the ServerManager
Management Console URL.

2 i. ServerManager URL is invalid

3 ii. EnterpriseOne User is not defined in ServerManager

4 iii. EnterpriseOne WIN32 client and ServerManager have different

security servers

5 1. Trusted Domain must be set.

 1 2. Failed to retrieve BSSV Server List

0 a. JDBJ.INI on the WIN32 client is not correct.

1 b. JDBC drivers do not exist in the <EnterpriseOne install>/MISC folder

Note: Make sure you have both E1 database jdbc driver and SQL jdbc driver
(JDELocal is MSDE or SSE and it uses SQL jdbc driver to connect).

2 c. ServerManager agent is not running

3 d. F98825E does not exist

When searching in the jasdebug log search for tags [PACKAGEBUILD]

The first thing it will check is:
Is the user valid?
[PACKAGEBUILD] Entering isUserValidInSCF
[DEBUG ] - [3680][PACKAGEBUILD] Validating E1 User JDE with SCF
Management Console URL: http://dencmassive.mlab.jdedwards.com:8999/manage
Look for this message in the log:
[PACKAGEBUILD] E1 User is an authorized SCF user.

The second thing it will do is to pull back the list of apps where it can deploy to:
[PACKAGEBUILD] Entering getAppServerListToDeploy.

Then returns with an XML document that looks like this, showing the machineName,
instanceName, appserverType and deployStatus.

[PACKAGEBUILD] <SBFAppServerList>
<AppServer agentStatus="Running" machineName="dencmassive"
instanceName="BSSV_Server" appserverType="oas_1013" installedPackage="None"
deployStatus="None"/>

The next thing it does is insert the information into a table using jdbj (table = F98825E)
[PACKAGEBUILD] Adding server list to F98825E.

Make sure that the appropriate jdbc drivers are found in the following directory

E812\MISC

Also, make sure that the following section is correct in the jde.ini file

[LOCALWEB]
Spec Datasource=Local - DV812

And there is a datasource by that name in System datasources

Next a UBE will run to complete the deployment into the container within Server
Manager
R98825F make sure there is an OCM record for DV812 *Public so that is will run
properly.

The UBE then goes back to the deployment server package directory for BSSV and
under the sbfjar directory, adds a manifest, the appropriate ear file for appserver. Then
packages this up in a .jar file and deploys to Server manager container. Finally, it deletes
the files from this folder (sbfjar).

Jasdebug logs will show: in Process until it completes can take a few minutes to
complete.

Once deployed to BSSV server, then need to bounce HTTP service on that machine.

To check connectivity to BSSV server:

- Go into E1 access application P90701A

- Take the Form exit for Server Configuration
- Select System 812
- Do a find if there is no record for BSSV server type, then you will need to add it
so it looks like this:
Port number can be found through Server manager tool Instance BSSV > Runtime
Settings > Incoming JDENET Port = 6114
Once you have configured and activated, you can select the Row exit for Ping Server to
make sure that the E1 server is able to communicate with the BSSV server.

Although all configuration files should be changed using Server Manager here is the
location of these files:
C:\agent\targets\BSSV_Server\config