nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD 5.5.1 use of OpenAPI - Install Order

gsumers22texas

I'd like to get confirmation of the order of installing OD 5.5.1 components to be installed on OD 5.5.2 (solaris)-

we will be using TeamSite OpenAPI with OpenDeploy instead of the Operations Server --> OD Base and OD Admin server will be installed to the TeamSite server

Do the "Using TeamSite OpenAPI with OpenDeploy" configuration instructions supersede/replace Step 1 in the Component Installation Order? A little bit confusing in that these instructions are presented at end of overall installation instructions in the OD admin manual-

thus, making the sequence as follows:
1. Perform "Using TeamSite OpenAPI with OpenDeploy" steps as documented on Page 62 of OD admin manual
2. Install OD Administration Server
3. Install OD Base Server
4. Quit Installation (we will install Receiver later)
5. Apply OD 5.5.1 SP1
6. Apply OD 5.5.1 SP2
7. Apply OD Patch # 1253

Thanks for all replies and sharing any experience-

Find more posts tagged with

Comments

Adam Stoller

If you are using TeamSite 5.5x's OpenAPI then you do not install the OpenDeploy Operations Server - just install the Admin Server and the Base Server (for your TeamSite / Base Server installation).

For all other OpenDeploy installations after that (Base Server or Receiver) you would only install the OpenDeploy server (again, Base Server or Receiver) component and during the installation you would indicate the platform type of the AdminServer you already installed.

Okay?

--fish
(Interwoven, Curriculum Development)

gsumers22texas

thanks for info ghoti-
we'd figured out not to install the Operations Server (skip Step 1) - but when to do the "Using TeamSite OpenAPI with OpenDeploy" instructions on page 62? is this done before installing the Admin Server ? before / after the install of the Base Server? or does it not matter when these steps are performed?

Adam Stoller

Hmm - I don't remember going through those steps - but then again I was kind of an early adopter and I just might have forgotten.

I would recommend performing those steps before installing the Admin Server component. Some of those steps are really just sanity-checking steps (e.g. "Ensure the OpenAPI server is running") Unless you have reason to believe that TeamSite is not currently functioning, you can probably skip to the 3rd step in those instructions to make sure that the OpenDeploy-specific roles are created.

Step 4 gets a bit confusing because that really jumps you back to the inital steps of installing the software (AdminServer and Base Server) afterwhich you go to p. 67 and take care of configuring your bootstrap administratory, and then you should explicitly run iwreset -ui (or -a if TeamSite isn't running)

Hmm - yeah, it is kind of confusing. I believe there is some work going on to make the installation procedure a bit more automated so you don't have to worry about jumping back-and-forth through the manual in the future.

So - to summarize:
p. 57-58 or 62-63 (steps 1-4)
p. 53-54 (Administration Server + Base Server)
p. 67-69 (Configuring the Bootstrap Administrator)
p 58 or 63 (step 5)

--fish
(Interwoven, Curriculum Development)

gsumers22texas

thanks for feedback ghoti-
good to know I'm not only one who thinks the install steps are a little bit cludgey-

a question about one of the sanity-checking steps- Step 1 of Page 57 says to ensure that the OpenAPI server software is running. Consulting the Administration chapter of the OpenAPI Dev Guide (page 89), it says to do this with a $ps -ef | grep iwservletd -
we do this, but get no results, just the grep itself:

# ps -ef | grep iwservletd
root 20539 20357 0 14:49:02 pts/2 0:00 grep iwservletd

we run iwreset -a, and it logs that the servlet is stopping and starting okay:

# cat /docs/iw-home/bin/nohup.out
Interwoven Servlet Engine stopping ...
Interwoven Proxy Server stopping ...
Interwoven Web Daemon stopping ...
Interwoven Web Daemon starting ...
Interwoven Proxy Server starting ...
Interwoven Servlet Engine starting ...
#

this does mean that the OpenAPI server is not running, doesn't it? or is there a flaw in the "ps -ef | grep iwservletd" method of verifying the OpenAPI server? the OpenAPI manual doesn't give an example of what should be returned from the ps? if it does mean OpenApi isn't running, wouldn't we be having other problems? we can login to teamsite and the teamsite admin ui without problem?

gsumers22texas

another tidbit of information is that the iw-home/local/logs/iwui/servletd.log file doesn't seem to exist (nor even the .../iwui/... subdir)- does this typically indicate a problem with OpenApi with the TeamSite install?

fyi, I have also opened a Support Case to investigate this but was hoping devnet could help in quicker fashion

gsumers22texas

and another piece of info that suggests OpenAPI server IS running- performed step 3 in the "Using TeamSite OpenAPI with OpenDeploy" config steps (pg. 58 on the OD Admin 5.5.2 guide) and we get the "Item Already Exists " for both od-admin and od-user roles.

in summary:

Several things we do suggest OpenAPI server IS running:
1. login to UI and Admin UI works okay
2. Step 3 as indicated above returns message as expected as thought OpenAPI already "knows" these OD roles
3. iwreset shows no errors and states servlet is stopping and servlet is starting

Several things we do suggest OpenAPI server IS NOT running:
1. no iwservletd entry when we do a $ps -ef | grep iw (as root)
2. no OpenAPI log file or iwui subdirectory in the .../logs/ directory
3. no find when searching for "openapi" in iwtrace.log, iwserver.log or iwinstall.log

any opinions as to what evidence is the most reliable before we proceed to install OD admin and base servers?

strsprint_lxf_x86.inf.txt

Adam Stoller

ps -ef | grep iwservletd

First, I wouldn't use the OpenAPI Developer's Guide for figuring out instructions for OpenDeploy installation, but the instructions in the OpenDeploy Administrator's Guide (p. 117) have been superceded and (somewhat obliquely) covered in the Release Notes (p. 31) "OpenAPI Consolidated into Administration Server for TeamSite 5.5.1 and Later" - essentially if TeamSite is running, OpenAPI is running - don't look for a separate process.

iw-home/local/logs/iwui/servletd.log

I'm not sure where you picked this up (not in the OpenDeploy manual or Release Notes) - but that path is Windows-specific - on Unix, the default path for the log file would be in /var/adm/iwui/servletd.log

As regards to your summary - the best way that I can think of to determine if OpenAPI is running (TeamSite 5.5x) before trying to do an OpenDeploy installation, is to login to the TeamSite GUI. If you can do that, OpenAPI is running.

--fish
(Interwoven, Curriculum Development)

gsumers22texas

great response ghoti-
let me provide some answers to your questions so you can pass along to documetation folks (and for others who start into this same maze)

we were using the OpenAPI DG only to figure out how to verify OpenAPI server, as set forth in the OD Admin Config guide (step 1 on page 62) since there wasn't an example given in the OD manual on how to do this

the OpenAPI Dev Guide, page 91 states the following:
The OpenAPI server logs startup and error information (as long as TeamSite servlet logging is turned
on) in:
• iw-home/local/logs/iwui/servletd_out (Windows).
• iw-home/local/logs/iwui/servletd.log (Unix).

so I thought that servletd.log was the right file to search for- and indeed it was in /var/adm/iwui/ location you specified, so it appears the OpenAPI DG is out of whack

Many thanks for confirming my summary- I had always assumed that being able to log in to TS was best indicator, but no manuals seem to state this, they all indicate you should ps for a seperate daemon (iwservletd or IWServiceServer) that our ps never seems to return- it was a little bit "extra" frustrating that all of these example ps -ef | grep **** in the product docs never showed example of expected results although other ps -ef examples for other daemons (iwserver, iwproxy, etc) did ???

Adam Stoller

I've passed the information along to our documentors.
Thanks for sticking with it and clearly explaining the experience.

--fish
(Interwoven, Curriculum Development)